Triple
T24070811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ishi Wilderness (part) |
E596220
|
entity |
| Predicate | hasEthnicGroupAssociated |
P147326
|
FINISHED |
| Object | Yahi |
—
|
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: Yahi | Statement: [Ishi Wilderness (part), hasEthnicGroupAssociated, Yahi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEthnicGroupAssociated Context triple: [Ishi Wilderness (part), hasEthnicGroupAssociated, Yahi]
-
A.
hasEthnicGroupType
Indicates that an entity is associated with, characterized by, or classified according to a particular type or category of ethnic group.
-
B.
isUsedByEthnicGroup
Indicates that something (such as an object, practice, or resource) is utilized or employed by a particular ethnic group.
-
C.
hasEthnicGroupDocumented
chosen
Indicates that an entity has a specific ethnic group recorded or documented as being associated with it.
-
D.
mayBelongToEthnicGroup
Indicates that an entity is possibly, but not certainly, a member of a specified ethnic group.
-
E.
hasRecognizedEthnicGroup
Indicates that an entity includes or is associated with an ethnic group that is officially or socially recognized as distinct.
- 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_69e288c3999c8190809b282a04813dec |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1db191d288190af438be742e02252 |
completed | April 29, 2026, 10:19 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:41 p.m.