Triple
T429948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mexican Spanish |
E9690
|
entity |
| Predicate | hasRegionalVariant |
P5595
|
FINISHED |
| Object | Yucatec Mexican 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: Yucatec Mexican Spanish | Statement: [Mexican Spanish, hasRegionalVariant, Yucatec Mexican Spanish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionalVariant Context triple: [Mexican Spanish, hasRegionalVariant, Yucatec Mexican Spanish]
-
A.
regionalVariantOf
Indicates that one entity is a version or form of another that is specific to a particular geographic region or locale.
-
B.
languageVariant
chosen
Indicates that one language is a variant, dialect, or localized form of another language.
-
C.
hasRegionalIdentity
Indicates that an entity possesses or is associated with a specific regional or local identity.
-
D.
hasRegionCode
Indicates that an entity is associated with a specific regional identifier or code.
-
E.
recognizedRegionalLanguage
Indicates that a language holds officially recognized status within a specific region or subnational jurisdiction.
- 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_69a2e801e1d48190b505d1dd336b52ac |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2eeedf68c81908473d6c6600961bd |
completed | Feb. 28, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69a2edd7a3608190b8785c7b7205f6c1 |
completed | Feb. 28, 2026, 1:29 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.