Triple
T34868822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Obubra town |
E1005092
|
entity |
| Predicate | secondarySubdivisionType |
P199274
|
FINISHED |
| Object | local government area |
—
|
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: local government area | Statement: [Obubra town, secondarySubdivisionType, local government area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondarySubdivisionType Context triple: [Obubra town, secondarySubdivisionType, local government area]
-
A.
subdivisionType0
Indicates that the referenced entity is classified as the primary (level 0) type of administrative or territorial subdivision within a larger jurisdiction.
-
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.
categorySubdivision
Indicates that one category functions as a subdivision or subcategory within another broader category.
-
E.
hasTypeOfSubdivision
Indicates that one administrative or territorial unit is classified as a specific kind or category of subdivision.
- 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_69f76dbb678081909a247b9b5e1a73ac |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff29d831b881908d485609e0fc1d0b |
completed | May 9, 2026, 12:34 p.m. |
| PD | Predicate disambiguation | batch_69ff28f9f9e4819087f3402735de66c7 |
completed | May 9, 2026, 12:30 p.m. |
| PDg | Predicate description generation | batch_69ff29d77f48819085304ed5e92eb906 |
completed | May 9, 2026, 12:34 p.m. |
Created at: May 3, 2026, 4 p.m.