Triple
T138763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chemehuevi people |
E2805
|
entity |
| Predicate | historicalLifestyle |
P5380
|
FINISHED |
| Object | semi-nomadic |
—
|
LITERAL 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: semi-nomadic | Statement: [Chemehuevi people, historicalLifestyle, semi-nomadic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalLifestyle Context triple: [Chemehuevi people, historicalLifestyle, semi-nomadic]
-
A.
historicalOrigin
Indicates the relationship by which one entity serves as the source, origin, or starting point in history for another entity.
-
B.
historicalImpact
Indicates the influence or lasting effects that an entity, event, or action has had on subsequent history or historical developments.
-
C.
partOfHistoryOf
Indicates that one entity forms a component, episode, or contributing element within the historical development or narrative of another entity.
-
D.
historicalForm
Indicates that one entity is an earlier or historically attested form or variant of another entity.
-
E.
historicalAssessment
Indicates an evaluation or judgment of something based on its historical context, significance, or development over time.
- 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_69a2521e35c08190b28e5c9f1e3c9b59 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a257a800148190be119d1d075869b8 |
completed | Feb. 28, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69a25652efdc8190b85b33735a9e6370 |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a257101060819094db0f3a3a72f312 |
completed | Feb. 28, 2026, 2:46 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.