Triple
T38332451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nüümü |
E1037857
|
entity |
| Predicate | affectedByHistoricalEvent |
P145803
|
FINISHED |
| Object | California Indian Wars |
—
|
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: California Indian Wars | Statement: [Nüümü, affectedByHistoricalEvent, California Indian Wars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectedByHistoricalEvent Context triple: [Nüümü, affectedByHistoricalEvent, California Indian Wars]
-
A.
facedHistoricalImpact
Indicates that an entity has experienced or been subjected to a significant influence, consequence, or change resulting from historical events or processes.
-
B.
impactOfNotableEvent
chosen
Indicates the causal influence or consequences that a specific notable event has on an entity, situation, or outcome.
-
C.
hasHistoricalEvent
Indicates that a historical event occurred in, is associated with, or is relevant to a particular entity.
-
D.
historicalImpact
Indicates the influence or lasting effects that an entity, event, or action has had on subsequent history or historical developments.
-
E.
hasHistoricSignificanceFor
Indicates that something holds notable historical importance or relevance for a particular entity or group.
- 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_69f76e20d65c81909619ac0dd85c56f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 3, 2026, 4:30 p.m.