Triple
T139104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Squaw Valley |
E2812
|
entity |
| Predicate | renamingReason |
P2136
|
FINISHED |
| Object | removal of derogatory term "squaw" |
—
|
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: removal of derogatory term "squaw" | Statement: [Squaw Valley, renamingReason, removal of derogatory term "squaw"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: renamingReason Context triple: [Squaw Valley, renamingReason, removal of derogatory term "squaw"]
-
A.
nameChangeReason
chosen
Indicates the reason or justification for a change in an entity’s name.
-
B.
reasonForRelocation
Indicates the underlying cause, motivation, or circumstance that led an entity to move from one location to another.
-
C.
reasonForMerger
Indicates the underlying cause, motivation, or justification for why two or more entities merged.
-
D.
renamedYear
Indicates the year in which an entity underwent a renaming or change of name.
-
E.
renamedTo
Indicates that an entity has been given a new name, specifying the target name it was changed to.
- 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_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_69a2565426c08190aab68e34a6a2d60e |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.