Triple
T4876779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ishi |
E109223
|
entity |
| Predicate | ethnicity |
P194
|
FINISHED |
| Object | Yahi |
E109223
|
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: Yahi | Statement: [Ishi, ethnicity, Yahi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yahi Context triple: [Ishi, ethnicity, Yahi]
-
A.
Yahi
chosen
The Yahi were a small Native American group from northern California, known for being among the last surviving independent Indigenous peoples in the region and for the story of Ishi, their last known member.
-
B.
Yakhin
Yakhin is a variant form of the biblical name Jachin, traditionally associated with one of the two pillars of Solomon’s Temple.
-
C.
Tayshet
Tayshet is a town in Irkutsk Oblast, Russia, known as a major railway junction in Siberia.
-
D.
Harauti
Harauti is an Indo-Aryan dialect of the Rajasthani language spoken primarily in the Hadoti region of Rajasthan, India.
-
E.
Haruna
Haruna was a Japanese Kongō-class fast battleship that served in the Imperial Japanese Navy during both World Wars and saw extensive action in the Pacific Theater.
- 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_69bd440e9d64819083e82cf33b4d9570 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6dbbc734819083b28a022e5690d6 |
completed | March 20, 2026, 3:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be6fb5da2c8190aeec7d6d11b12b11 |
completed | March 21, 2026, 10:15 a.m. |
Created at: March 20, 2026, 1:27 p.m.