Triple
T34758554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Igbepa |
E1002000
|
entity |
| Predicate | localGovernmentHeadquartersOf |
P76475
|
FINISHED |
| Object | none |
—
|
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: none | Statement: [Igbepa, localGovernmentHeadquartersOf, none]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localGovernmentHeadquartersOf Context triple: [Igbepa, localGovernmentHeadquartersOf, none]
-
A.
districtHeadquartersSince
Indicates the time from which a particular location has served as the administrative headquarters of a specified district.
-
B.
districtHeadquartersLocation
chosen
Indicates the place where the administrative headquarters of a district is located.
-
C.
provinceHeadquarters
Indicates that one entity serves as the main administrative or organizational headquarters for a province associated with the other entity.
-
D.
headquartersMunicipality
Indicates the municipality in which an organization’s main administrative headquarters is located.
-
E.
capitalCityHeadquarters
Indicates that the headquarters of an organization or entity is located in the capital city of a specified region or country.
- 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_69f76db0fb30819096709d43f9a1f45f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 3:59 p.m.