Triple
T29052892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agarfa woreda |
E735309
|
entity |
| Predicate | locatedInGovernmentRegion |
P96807
|
FINISHED |
| Object | Oromia Region |
—
|
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: Oromia Region | Statement: [Agarfa woreda, locatedInGovernmentRegion, Oromia Region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInGovernmentRegion Context triple: [Agarfa woreda, locatedInGovernmentRegion, Oromia Region]
-
A.
locatedInTheCountryGoverned
Indicates that one entity is situated within the geographical boundaries of a country that is governed or administered by another specified entity.
-
B.
locatedInNationCapitalRegion
Indicates that an entity is situated within the capital region of a specific nation.
-
C.
locatedInGovernmentBody
Indicates that an entity is situated within, or is part of, a specific governmental body or institution.
-
D.
locatedInStateOrRegion
chosen
Indicates that one entity is geographically situated within the boundaries of a specified state or region.
-
E.
locatedInGovernorateCapitalRegion
Indicates that an entity is situated within the capital region of a governorate.
- 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_69f077e64b88819094d37bdbca8191b3 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69ffebbd9bac8190b3dca4b7252a2278 |
completed | May 10, 2026, 2:21 a.m. |
| PD | Predicate disambiguation | batch_69ffe93120a08190a44bb64d052eda78 |
completed | May 10, 2026, 2:10 a.m. |
Created at: April 28, 2026, 10:09 a.m.