Triple
T581847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kumeyaay language |
E15074
|
entity |
| Predicate | hasLinguasphereCode |
P15767
|
FINISHED |
| Object | YUM-010 |
—
|
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: YUM-010 | Statement: [Kumeyaay language, hasLinguasphereCode, YUM-010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLinguasphereCode Context triple: [Kumeyaay language, hasLinguasphereCode, YUM-010]
-
A.
hasLinguisticCode
Indicates that an entity is associated with a specific linguistic identifier or code (such as a language or script code) that characterizes its linguistic properties.
-
B.
hasISO6393Code
Indicates that a language or linguistic entity is associated with a specific ISO 639-3 three-letter language code.
-
C.
isLanguageOf
Indicates that a particular language is used as the official or primary language associated with a given entity (such as a person, document, or region).
-
D.
hasLanguageCodeOnWikipedia
Indicates that a particular language is represented on Wikipedia by a specific language code.
-
E.
hasLanguageGroup
Indicates that an entity belongs to, is associated with, or is categorized under a particular language group.
- F. None of above. chosen
Provenance (4 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_69a4935783b8819082b77726ec10cc42 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49b84899881909d5b2b4e67e22d9b |
completed | March 1, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69a494c7f9008190bd8d05b4dc2a7c7f |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a4985a2d08819090947895d9439e06 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:33 p.m.