Triple
T30515552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kird |
E776554
|
entity |
| Predicate | relatedEthnonymLanguageContext |
P204052
|
FINISHED |
| Object | Zaza language |
E1873099
|
NE 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: Zaza language | Statement: [Kird, relatedEthnonymLanguageContext, Zaza language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedEthnonymLanguageContext Context triple: [Kird, relatedEthnonymLanguageContext, Zaza language]
-
A.
relatedEthnonymNote
Indicates that there is an explanatory note describing how this ethnonym is related to another ethnonym or term.
-
B.
hasEthnonymCountry
Indicates that an ethnonym (a name for an ethnic group or people) is associated with or pertains to a specific country.
-
C.
opponentEthnonyms
Indicates that one party refers to another party using ethnonyms that mark them as an opponent or adversarial group.
-
D.
ethnonymLanguageFamily
Indicates a relationship where an ethnonym is associated with the language family traditionally spoken or linked to that ethnic group.
-
E.
hasEthnolinguisticContext
Indicates that something is associated with, shaped by, or understood within a specific ethnolinguistic (cultural and language-based) context.
- F. None of above. chosen
Provenance (5 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_69f2249b23c4819087fa85496d92f43f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a03142a3a7081909bcfb683b44e2217 |
completed | May 12, 2026, 11:51 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2856eb4d5881909521294dc6f47330 |
completed | June 9, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_6a031400af808190a72abf095e96c151 |
completed | May 12, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_6a03142984848190b35c2636c73376af |
completed | May 12, 2026, 11:51 a.m. |
Created at: April 29, 2026, 8:16 p.m.