Triple
T38113373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PDP |
E951719
|
entity |
| Predicate | hasStateLevelPresence |
P200340
|
FINISHED |
| Object | Nigerian state governments |
—
|
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: Nigerian state governments | Statement: [PDP, hasStateLevelPresence, Nigerian state governments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStateLevelPresence Context triple: [PDP, hasStateLevelPresence, Nigerian state governments]
-
A.
hasMajorStatePresence
chosen
Indicates that an entity maintains a significant operational or influential presence within a particular state.
-
B.
hasStateOrDistrict
Indicates that an entity is associated with, located in, or belongs to a particular state or district.
-
C.
hasStateOf
Indicates that an entity possesses, exhibits, or is currently in a particular condition, status, or mode.
-
D.
hasProvinceStatus
Indicates that an entity holds the administrative or political status of a province within a larger territorial or governmental system.
-
E.
hasStateOrIsland
Indicates that one entity possesses, includes, or is associated with a particular state or island as part of its composition, location, or jurisdiction.
- 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_69f76f07734c8190814e937e12257a78 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a00a846a8f881908b073ad13a5af6ca |
completed | May 10, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_6a00a7aae194819085e1a2fd406f7922 |
completed | May 10, 2026, 3:43 p.m. |
Created at: May 3, 2026, 4:21 p.m.