Triple
T23360673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nso |
E593173
|
entity |
| Predicate | hasEthnicCluster |
P90751
|
FINISHED |
| Object | Tikar-related 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: Tikar-related peoples | Statement: [Nso, hasEthnicCluster, Tikar-related peoples]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEthnicCluster Context triple: [Nso, hasEthnicCluster, Tikar-related peoples]
-
A.
hasEthnicScope
Indicates that something is relevant or applicable specifically to a particular ethnic group or ethnic context.
-
B.
hasEthnicDivision
Indicates that a group, region, or entity is characterized by internal divisions or distinctions based on ethnicity.
-
C.
hasEthnicGroupType
Indicates that an entity is associated with, characterized by, or classified according to a particular type or category of ethnic group.
-
D.
hasRecognizedEthnicGroup
Indicates that an entity includes or is associated with an ethnic group that is officially or socially recognized as distinct.
-
E.
ethnolinguisticCluster
chosen
Indicates a relationship where entities are grouped together based on shared ethnic and linguistic characteristics, treating them as part of the same ethnolinguistic cluster.
- 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_69e25d24d2a4819092e6ede74c2a918d |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a0a730f8819088fec53a43b063f8 |
completed | April 29, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:30 p.m.