Triple
T31225083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iraqi territorial waters |
E796115
|
entity |
| Predicate | coastlineGovernorate |
P171363
|
FINISHED |
| Object | Basra Governorate |
—
|
NE NERFINISHED |
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: Basra Governorate | Statement: [Iraqi territorial waters, coastlineGovernorate, Basra Governorate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coastlineGovernorate Context triple: [Iraqi territorial waters, coastlineGovernorate, Basra Governorate]
-
A.
coastlineAssociation
Indicates an association between an entity and a coastline, such as adjacency, alignment, or functional connection to that coastal boundary.
-
B.
countryCoastlineOf
Indicates that a country has the specified coastline as part of its national territory or boundary.
-
C.
coastalState
Indicates that a state has a coastline adjacent to a sea or ocean, giving it maritime access and jurisdiction over nearby coastal waters.
-
D.
coastlineFeature
Indicates that a geographic entity is a specific type of feature located along or forming part of a coastline.
-
E.
hasCoastline
Indicates that a geographic entity is bordered by and directly touches a sea or ocean along part of its boundary.
- F. None of above. chosen
Provenance (4 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_69f224da98f88190ab32f690cce5d303 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69dfbf6ac8190ba2e6fc0adfd8b73 |
completed | May 3, 2026, 12:59 a.m. |
Created at: April 29, 2026, 9:10 p.m.