Triple
T38668865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Idua Oron |
E940528
|
entity |
| Predicate | traditionalInhabitantsOf |
P100744
|
FINISHED |
| Object | part of the coastal Akwa Ibom region |
—
|
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 the coastal Akwa Ibom region | Statement: [Idua Oron, traditionalInhabitantsOf, part of the coastal Akwa Ibom region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalInhabitantsOf Context triple: [Idua Oron, traditionalInhabitantsOf, part of the coastal Akwa Ibom region]
-
A.
traditionalPeople
chosen
Indicates that the subject consists of or is associated with people who maintain long-established customs, beliefs, or ways of life.
-
B.
historicallyInhabitedBy
Indicates that a place or region was inhabited by a particular group or population during some period in the past.
-
C.
inhabitedBy
Indicates that a place or location is lived in or occupied by a particular individual, group, or species.
-
D.
traditionallyResidesIn
Indicates that an entity customarily lives or has its long-established home in a particular place or region.
-
E.
inhabitantOf
Indicates that an entity lives in or resides within a specified place or location.
- 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_69f76edfde348190bf6529d9f49ecd62 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a001540d4f881908a4688881875e774 |
completed | May 10, 2026, 5:18 a.m. |
| PD | Predicate disambiguation | batch_6a0014a8cdd88190a67a90a2df2c5e18 |
completed | May 10, 2026, 5:16 a.m. |
Created at: May 3, 2026, 4:33 p.m.