Triple
T30515555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kird |
E776554
|
entity |
| Predicate | hasEthnonymTarget |
P57538
|
FINISHED |
| Object | Zaza people |
—
|
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: Zaza people | Statement: [Kird, hasEthnonymTarget, Zaza people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEthnonymTarget Context triple: [Kird, hasEthnonymTarget, Zaza people]
-
A.
hasEthnonymSource
Indicates that an ethnonym (a name for an ethnic group or people) is derived from, or based on, a particular source term, name, or linguistic form.
-
B.
hasEthnonymMeaning
Indicates that one entity is the meaning or semantic interpretation of an ethnonym (a name for an ethnic group) associated with another entity.
-
C.
hasEthnonymVariant
chosen
Indicates that one ethnonym is an alternative or variant form of another ethnonym referring to the same ethnic group.
-
D.
hasEthnonymCountry
Indicates that an ethnonym (a name for an ethnic group or people) is associated with or pertains to a specific country.
-
E.
hasPrimaryEthnonym
Indicates that an entity is associated with its main or most commonly used ethnonym (ethnic group name) as its primary designation.
- 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_69f2249b23c4819087fa85496d92f43f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 29, 2026, 8:16 p.m.