Triple
T26164533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sir Creek dispute |
E654210
|
entity |
| Predicate | hasDisputedAreaType |
P40419
|
FINISHED |
| Object | tidal estuary |
—
|
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: tidal estuary | Statement: [Sir Creek dispute, hasDisputedAreaType, tidal estuary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDisputedAreaType Context triple: [Sir Creek dispute, hasDisputedAreaType, tidal estuary]
-
A.
hasDisputedSector
Indicates that there exists a sector or area whose ownership, control, or status between the related entities is contested or not mutually agreed upon.
-
B.
hasDisputeType
chosen
Indicates that an entity is associated with a particular category or type of dispute.
-
C.
hasDisputedCircumscription
Indicates that there is disagreement or uncertainty about how the boundaries or scope of something are formally defined or delimited.
-
D.
hasDisputedStatus
Indicates that the status or classification of something is contested, uncertain, or not universally agreed upon.
-
E.
hasDisputedComponent
Indicates that an entity includes a component whose ownership, status, validity, or characteristics are contested or not mutually agreed upon.
- 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_69ee5b44391c81908bdbd8813ba9aa99 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 26, 2026, 8:32 p.m.