Triple
T3337531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dinjii Zhu’ Ginjik |
E70173
|
entity |
| Predicate | hasEthnonymType |
P4709
|
FINISHED |
| Object | self-designation |
—
|
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: self-designation | Statement: [Dinjii Zhu’ Ginjik, hasEthnonymType, self-designation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEthnonymType Context triple: [Dinjii Zhu’ Ginjik, hasEthnonymType, self-designation]
-
A.
hasEthnonymMeaning
Indicates that one entity is the meaning or semantic interpretation of an ethnonym (a name for an ethnic group) associated with another entity.
-
B.
ethnonym
chosen
Indicates that one entity is the name of an ethnic group used to refer to the people associated with another entity.
-
C.
hasEthnicCharacteristic
Indicates that an entity possesses or is associated with a particular ethnic characteristic or identity.
-
D.
hasEthnologueEntry
Indicates that there exists an entry for the subject in the Ethnologue language reference resource.
-
E.
hasExonym
Indicates that one entity is known by an alternative name or designation in another language or cultural context.
- 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_69ad85a24f208190bcf83131bfed3521 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb1bc31b4819085f01e0b5a7cbc5d |
completed | March 8, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69ada42c2ba8819091136805ce17b39d |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:12 p.m.