Triple
T15339588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yahi |
E366753
|
entity |
| Predicate | neighboringGroup |
P5965
|
FINISHED |
| Object | Yana (Central Yana) |
E479416
|
NE 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: Yana (Central Yana) | Statement: [Yahi, neighboringGroup, Yana (Central Yana)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yana (Central Yana) Context triple: [Yahi, neighboringGroup, Yana (Central Yana)]
-
A.
Northern Yana
Northern Yana is a now-extinct dialect of the Yana language once spoken by Indigenous people in northern California.
-
B.
Central Yana
chosen
Central Yana were a Native American group of the Yana people of northern California, culturally and linguistically related to the Yahi.
-
C.
Southern Yana
Southern Yana is a now-extinct dialect of the Yana language once spoken by Indigenous people in northern California.
-
D.
Yana
Yana is a small family of extinct Native American languages once spoken in northern California.
-
E.
Yana
Yana is a professor character from the Doctor Who universe whose true identity is central to a major plot twist.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d85a1355608190a6673ddb67231d54 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e12eb7c8190944a260aa1aa9156 |
completed | April 16, 2026, 1:40 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff133f242c819099ec5288ae4a622f |
completed | May 9, 2026, 10:58 a.m. |
Created at: April 10, 2026, 3:17 a.m.