Triple
T19429548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Keres |
E486072
|
entity |
| Predicate | distinctFrom |
P1612
|
FINISHED |
| Object | Western Keres |
—
|
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: Western Keres | Statement: [Eastern Keres, distinctFrom, Western Keres]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Western Keres Context triple: [Eastern Keres, distinctFrom, Western Keres]
-
A.
Western Keres
chosen
Western Keres is a Keresan Puebloan language spoken by the Keres people of western New Mexico.
-
B.
Eastern Keres
Eastern Keres is a Keresan Puebloan language traditionally spoken by Native American communities in central New Mexico.
-
C.
Western Rarámuri
Western Rarámuri is a principal regional variety of the Rarámuri (Tarahumara) language spoken by Indigenous communities in the Sierra Madre region of northern Mexico.
-
D.
Southwestern Pomo
Southwestern Pomo, also known as Kashaya Pomo, is a Pomoan language traditionally spoken by the Kashaya people of the Sonoma County coastal region in Northern California.
-
E.
Central Wintun
Central Wintun is an indigenous Wintuan language of Northern California, traditionally spoken by the Nomlaki people.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6321b78d08190b86cef7c60cbb61c |
completed | April 20, 2026, 2:03 p.m. |
Created at: April 10, 2026, 1:37 p.m.