Triple
T18990426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jug Bay Wetlands Sanctuary |
E464666
|
entity |
| Predicate | managingInterest |
P87560
|
FINISHED |
| Object | local government |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: local government | Statement: [Jug Bay Wetlands Sanctuary, managingInterest, local government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managingInterest Context triple: [Jug Bay Wetlands Sanctuary, managingInterest, local government]
-
A.
managesInterestsIn
chosen
Indicates that one entity is responsible for overseeing, handling, or administering the interests or stakes of another entity.
-
B.
interestType
Indicates the specific category or nature of interest that one entity has in relation to another or to a subject.
-
C.
subjectInterest
Indicates that the subject has an interest in, or is concerned with, the object.
-
D.
representsInterestOf
Indicates that one entity expresses, holds, or embodies an interest, concern, or stake in another entity or subject.
-
E.
recognizedInterest
Indicates that one entity has formally acknowledged or identified another entity’s interest in something as valid or relevant.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d8dd01a56c81909694a128c66b21d7 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6632cb08190a28f6ab74c2156d8 |
completed | April 20, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f88e0c81908cb20f08bf24cd32 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:01 p.m.