Triple
T10569125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teda people |
E249431
|
entity |
| Predicate | macroEthnicGroup |
P45393
|
FINISHED |
| Object | Saharan 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: Saharan peoples | Statement: [Teda people, macroEthnicGroup, Saharan peoples]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: macroEthnicGroup Context triple: [Teda people, macroEthnicGroup, Saharan peoples]
-
A.
otherEthnicGroup
Indicates that one entity belongs to a different ethnic group than the other entity.
-
B.
ethnicGroupBase
Indicates that one entity serves as the primary or foundational ethnic group from which another entity is derived, associated, or defined.
-
C.
holderEthnicity
Indicates the ethnic background or group to which the holder of something (e.g., a document, account, or item) belongs.
-
D.
dominantEthnicGroups
Indicates that the specified ethnic groups hold primary demographic, cultural, or political prominence within a given region or population.
-
E.
containedEthnicGroup
chosen
Indicates that one entity (typically a larger group, region, or population) includes or encompasses a particular ethnic group within it.
- 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_69d381c8bd708190acf3d275c908251e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d52730fd4481908b3f4eb80ca209f2 |
completed | April 7, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69d51901ff6c819095e7b528170a69dc |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:37 p.m.