Triple
T6185306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nineveh Governorate |
E138039
|
entity |
| Predicate | hasGovernorateCode |
P69552
|
FINISHED |
| Object | IQ-NI |
—
|
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: IQ-NI | Statement: [Nineveh Governorate, hasGovernorateCode, IQ-NI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGovernorateCode Context triple: [Nineveh Governorate, hasGovernorateCode, IQ-NI]
-
A.
includesGovernorate
Indicates that one administrative region or entity contains or encompasses a governorate within its boundaries.
-
B.
governorateOrDistrict
Indicates that one administrative region is a governorate or district that encompasses, governs, or is otherwise the primary subnational division for another area or locality.
-
C.
hasRegionalGovernor
Indicates that a region is administered or overseen by a specific governor responsible for its governance.
-
D.
passesThroughGovernorate
Indicates that something (such as a route, boundary, or flow) traverses or goes through a particular governorate.
-
E.
governorateOf
Indicates that one entity is the governorate (administrative region) to which another entity belongs or is located within.
- 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_69c008a8fd408190b7ec6e42934974a6 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062150fc48190877240abe6b6c636 |
completed | March 22, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69c055fa0a808190bda37832e3ac150c |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c056c87340819088003f427706ebf8 |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:19 p.m.