Triple
T19613918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amanyanabo of Nembe |
E470806
|
entity |
| Predicate | governsPeople |
P82687
|
FINISHED |
| Object | Nembe communities in Bayelsa State |
—
|
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: Nembe communities in Bayelsa State | Statement: [Amanyanabo of Nembe, governsPeople, Nembe communities in Bayelsa State]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsPeople Context triple: [Amanyanabo of Nembe, governsPeople, Nembe communities in Bayelsa State]
-
A.
areGovernedBy
Indicates that one or more entities are under the authority, control, or administration of a governing body or ruler.
-
B.
governingPeople
chosen
Indicates a relationship where one entity holds authority over and exercises control or administration of another group of people.
-
C.
governedFor
Indicates that one entity exercised governing authority or administrative control on behalf of, or in the interest of, another entity.
-
D.
governedEntity
Indicates that one entity exercises authority, control, or governance over another entity.
-
E.
governedIn
Indicates that one entity exercised governing authority or administrative control within a specified place 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_69d8e510fa248190b7afb274a1d4cf73 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640ce272481909688527f72d2c976 |
completed | April 20, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69e514e166dc8190a0f147e0b4c8bbe7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:43 p.m.