Triple
T3275722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guna language |
E68751
|
entity |
| Predicate | autonymMeaning |
P1966
|
FINISHED |
| Object | language of the people |
—
|
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: language of the people | Statement: [Guna language, autonymMeaning, language of the people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: autonymMeaning Context triple: [Guna language, autonymMeaning, language of the people]
-
A.
autonymLanguageCode
Indicates that the associated language code is the one used by a language to refer to itself (its autonym).
-
B.
hasEndonym
Indicates that an entity has a name or designation used by native speakers or within its own local language or community.
-
C.
hasEthnonymMeaning
Indicates that one entity is the meaning or semantic interpretation of an ethnonym (a name for an ethnic group) associated with another entity.
-
D.
ethnonym
Indicates that one entity is the name of an ethnic group used to refer to the people associated with another entity.
-
E.
meaningOfNativeName
chosen
Indicates that one entity specifies the semantic meaning or translation of another entity’s native-language name.
- 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_69ad859b54f881909bf530d549caf2fd |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0110f1c8190ae60708b686cbbf9 |
completed | March 8, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69ada420167c81909b6e2702db296d9e |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:10 p.m.