Triple
T21710060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matlatzinca language |
E535877
|
entity |
| Predicate | shiftLanguage |
P4292
|
FINISHED |
| Object | Spanish |
—
|
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: Spanish | Statement: [Matlatzinca language, shiftLanguage, Spanish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shiftLanguage Context triple: [Matlatzinca language, shiftLanguage, Spanish]
-
A.
languageShift
chosen
Indicates a change in the primary language used by an entity, such as switching from one language to another over time or in a given context.
-
B.
navigationLanguage
Indicates the language used for navigation-related content, such as menus, directions, or interface controls.
-
C.
suffixLanguage
Indicates that one language is used as a suffix or ending element in the formation or representation of another language or linguistic expression.
-
D.
languageAffected
Indicates that one entity has an impact on, modifies, or influences the characteristics, usage, or status of a language.
-
E.
alternateLanguageName
Indicates that an entity has an additional name or label in a different language from its primary or default 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_69e0c46b44c0819088ab883ebd44e0e8 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efb5333c8481909d729fb3bc3c9bc5 |
completed | April 27, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:46 p.m.