Triple
T33778060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samor |
E865574
|
entity |
| Predicate | partOfEthnicGroupLanguage |
P155517
|
FINISHED |
| Object | Tugen language |
—
|
NE NERFINISHED |
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: Tugen language | Statement: [Samor, partOfEthnicGroupLanguage, Tugen language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfEthnicGroupLanguage Context triple: [Samor, partOfEthnicGroupLanguage, Tugen language]
-
A.
ethnicGroupLanguageOf
chosen
Indicates that a particular language is spoken by, associated with, or characteristic of a given ethnic group.
-
B.
commonInEthnicGroup
Indicates that something (such as a trait, condition, or characteristic) occurs with notable frequency within a specified ethnic group.
-
C.
ethnolinguisticGroups
Indicates a relationship where groups are categorized or associated based on shared ethnic and linguistic characteristics.
-
D.
ethnonymLanguageFamily
Indicates a relationship where an ethnonym is associated with the language family traditionally spoken or linked to that ethnic group.
-
E.
mayBelongToEthnicGroup
Indicates that an entity is possibly, but not certainly, a member of a specified ethnic group.
- 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_69f3498df6f88190bf9647ea4e4a956e |
completed | April 30, 2026, 12:22 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 1, 2026, 1:45 a.m.