Triple
T2957379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cora |
E79964
|
entity |
| Predicate | languagePolicyStatus |
P25828
|
FINISHED |
| Object | recognized indigenous language of Mexico |
—
|
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: recognized indigenous language of Mexico | Statement: [Cora, languagePolicyStatus, recognized indigenous language of Mexico]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languagePolicyStatus Context triple: [Cora, languagePolicyStatus, recognized indigenous language of Mexico]
-
A.
languagePolicyIssue
Indicates that there is a problem, conflict, or concern related to rules or practices governing language use.
-
B.
languagePolicyRegion
Indicates that a particular language policy applies within, or is associated with, a specific geographic or administrative region.
-
C.
hasLanguageStatus
chosen
Indicates that an entity has a particular status or condition regarding its language use, recognition, or classification.
-
D.
officialLanguageStatusSharedWith
Indicates that two entities share at least one official language in common.
-
E.
locationPolicy
Indicates a rule or constraint governing where an entity is allowed, required, or restricted to be located.
- 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_69ad8b1276588190a374a0b12e0f7bdf |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad992b33e081909d22a19d5064c47d |
completed | March 8, 2026, 3:43 p.m. |
| PD | Predicate disambiguation | batch_69ad960c5c8881909d679912bd7d78f3 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:57 p.m.