Triple
T13982277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Igala |
E336340
|
entity |
| Predicate | modernStateIntegration |
P25757
|
FINISHED |
| Object | part of Kogi State since 1991 |
—
|
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: part of Kogi State since 1991 | Statement: [Igala, modernStateIntegration, part of Kogi State since 1991]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernStateIntegration Context triple: [Igala, modernStateIntegration, part of Kogi State since 1991]
-
A.
modernState
Indicates that an entity functions as a contemporary, currently existing state or nation in the modern era.
-
B.
modernStateSuccessor
Indicates that one modern state is the legal, political, or historical successor to another earlier state.
-
C.
modernStateName
Indicates that an entity is identified by the name of the corresponding modern (current) state or country.
-
D.
modernClaimantState
Indicates that a state is the contemporary political entity that claims continuity with, or succession from, an earlier historical state.
-
E.
modernRegion
chosen
Indicates that an entity is located within or associated with a contemporary, present-day geographic or administrative region.
- 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_69d81c639e808190a0e4b4f3d31c6a59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2ea2e8808190a1203a6386224bd8 |
completed | April 14, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69dd465a21408190b912a42c50ffa0d9 |
completed | April 13, 2026, 7:39 p.m. |
Created at: April 9, 2026, 10:18 p.m.