Triple
T34868823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Obubra town |
E1005092
|
entity |
| Predicate | secondarySubdivision |
P171071
|
FINISHED |
| Object | Obubra Local Government Area |
—
|
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: Obubra Local Government Area | Statement: [Obubra town, secondarySubdivision, Obubra Local Government Area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondarySubdivision Context triple: [Obubra town, secondarySubdivision, Obubra Local Government Area]
-
A.
secondarySubdivisionType
Indicates the specific kind or category of a second-level administrative or geographic subdivision within a larger primary division.
-
B.
subdivisionAlternativeName
Indicates an alternative or variant name used to refer to a particular subdivision.
-
C.
primarySubdivisionOf
Indicates that one administrative or territorial unit is the main first-level subdivision within a larger political or geographic entity.
-
D.
localSubdivision
chosen
Indicates that one administrative or geographic area is a smaller, constituent part within a larger local jurisdiction or region.
-
E.
categorySubdivision
Indicates that one category functions as a subdivision or subcategory within another broader category.
- 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_69f76dbb678081909a247b9b5e1a73ac |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff2d22ffb48190ae58ddf3c7e02869 |
completed | May 9, 2026, 12:48 p.m. |
| PD | Predicate disambiguation | batch_69ff2ac2e1c4819096cc64e94aef2ff0 |
completed | May 9, 2026, 12:38 p.m. |
Created at: May 3, 2026, 4 p.m.