Triple
T12963277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enugu North |
E321199
|
entity |
| Predicate | stateCapitalLGAOf |
P107149
|
FINISHED |
| Object | Enugu State capital city |
—
|
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: Enugu State capital city | Statement: [Enugu North, stateCapitalLGAOf, Enugu State capital city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateCapitalLGAOf Context triple: [Enugu North, stateCapitalLGAOf, Enugu State capital city]
-
A.
stateCapitalRegion
Indicates that a region serves as the capital area or administrative seat for a particular state.
-
B.
stateCapitalConnection
chosen
Indicates a relationship where one entity is the capital city of a given state or is otherwise connected to that state in its role as capital.
-
C.
stateCapitalForRegionLocatedAt
Indicates that a city serves as the capital of a particular region and is geographically located at that region.
-
D.
capitalCityOfAssociatedState
Indicates that a city serves as the capital of the state with which another entity is associated.
-
E.
governsCapital
Indicates that a political authority or administrative body exercises governing control over a capital city.
- 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_69d80763bd6c819094437da5b20b01d2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69d97dba57988190b786ffed55687a72 |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:24 p.m.