Triple
T38028403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spanish Nevada |
E948840
|
entity |
| Predicate | predecessorInhabitant |
P125836
|
FINISHED |
| Object | Indigenous peoples of the Great Basin |
—
|
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: Indigenous peoples of the Great Basin | Statement: [Spanish Nevada, predecessorInhabitant, Indigenous peoples of the Great Basin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorInhabitant Context triple: [Spanish Nevada, predecessorInhabitant, Indigenous peoples of the Great Basin]
-
A.
predecessor
Indicates that one entity comes before another in an ordered sequence or succession.
-
B.
predecessorPopulation
Indicates that one population entity is the immediate prior version or state of another population entity in a temporal or evolutionary sequence.
-
C.
predecessorEstablished
Indicates that one entity was established before another, serving as its predecessor in origin or founding.
-
D.
originalInhabitant
chosen
Indicates that an entity was among the first or earliest residents of a particular place or territory.
-
E.
predecessorCulture
Indicates that one culture historically preceded and contributed to the development of another culture.
- 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_69f76efd1bc48190a729097fe5177b61 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe766490c081908c49c8cc07d0ae9b |
completed | May 8, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69fe75bb5f4481908572a5ffcbdc5154 |
completed | May 8, 2026, 11:46 p.m. |
Created at: May 3, 2026, 4:20 p.m.