Triple
T36020400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lone Pine Paiute-Shoshone Tribe |
E1041964
|
entity |
| Predicate | peoplehoodBasedIn |
P184337
|
FINISHED |
| Object | Owens Valley |
—
|
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: Owens Valley | Statement: [Lone Pine Paiute-Shoshone Tribe, peoplehoodBasedIn, Owens Valley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peoplehoodBasedIn Context triple: [Lone Pine Paiute-Shoshone Tribe, peoplehoodBasedIn, Owens Valley]
-
A.
peoplehood
Indicates a relationship in which individuals share a common collective identity, culture, or heritage that binds them together as a distinct people.
-
B.
inhabitantOf
Indicates that an entity lives in or resides within a specified place or location.
-
C.
regionOfHabitation
Indicates the geographic area or environment in which an entity typically lives or resides.
-
D.
believedToResideIn
Indicates that one entity is thought or assumed to live or be located in a particular place or region, without confirming this as a verified fact.
-
E.
residencyOf
Indicates that one entity serves as the place where another entity resides or lives.
- F. None of above. chosen
Provenance (4 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_69f76e2b981881908e4e160607fa82eb |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ad15f3b88190b7c9742a734fec5f |
completed | May 3, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69f7ab75387c819091afc3c2128eb903 |
completed | May 3, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69f7acad20388190b9b10270ca9bdfbc |
completed | May 3, 2026, 8:14 p.m. |
Created at: May 3, 2026, 4:07 p.m.