Triple
T24245452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Rarámuri |
E603353
|
entity |
| Predicate | isSpokenInRegion |
P7445
|
FINISHED |
| Object | Sierra Madre Occidental |
—
|
NE NERFINISHED |
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: Sierra Madre Occidental | Statement: [Northern Rarámuri, isSpokenInRegion, Sierra Madre Occidental]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSpokenInRegion Context triple: [Northern Rarámuri, isSpokenInRegion, Sierra Madre Occidental]
-
A.
isSpokenOn
Indicates that a particular language, phrase, or utterance is used or occurs during a specified time, event, or occasion.
-
B.
isSpokenInAdministrativeUnit
Indicates that a particular language is used or officially spoken within a specified administrative unit or region.
-
C.
areSpokenIn
chosen
Indicates that a particular language is used as a spoken means of communication within a specified region, community, or context.
-
D.
alsoInLanguageRegion
Indicates that two or more entities are located within or associated with the same language-defined geographic region.
-
E.
isSpokenLanguage
Indicates that a language is used primarily for oral communication by speakers, as opposed to being only written or symbolic.
- 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_69e2953f631c819097cbb421046bd417 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28b84707881908b358aa38fafb61a |
completed | April 29, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:04 a.m.