Triple
T21947644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isoko |
E541974
|
entity |
| Predicate | ethnolinguisticBranch |
P31853
|
FINISHED |
| Object | Edoid peoples |
—
|
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: Edoid peoples | Statement: [Isoko, ethnolinguisticBranch, Edoid peoples]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethnolinguisticBranch Context triple: [Isoko, ethnolinguisticBranch, Edoid peoples]
-
A.
ethnolinguisticGroups
Indicates a relationship where groups are categorized or associated based on shared ethnic and linguistic characteristics.
-
B.
ethnoLinguisticRegionOf
Indicates that a region is defined or characterized by the shared ethnic and linguistic identity of the group associated with it.
-
C.
ethnolinguisticCluster
Indicates a relationship where entities are grouped together based on shared ethnic and linguistic characteristics, treating them as part of the same ethnolinguistic cluster.
-
D.
linguisticSubgroup
chosen
Indicates that one linguistic group forms a subordinate or specialized subset within a larger linguistic group or family.
-
E.
languageFamilyBranchOf
Indicates that one language family branch is a sub-group or subdivision within a larger language family.
- 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_69e0c47ef0e48190a50e1bcc43f4b3fd |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1243a2f788190bd4625fa79888696 |
completed | April 28, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e6f601f2188190893bcdde0cf58ad6 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 7:57 p.m.