Triple
T1957458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whiteface Mountain |
E42301
|
entity |
| Predicate | hasEventHistory |
P2107
|
FINISHED |
| Object | 1980 Winter Olympics alpine skiing venue |
—
|
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: 1980 Winter Olympics alpine skiing venue | Statement: [Whiteface Mountain, hasEventHistory, 1980 Winter Olympics alpine skiing venue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEventHistory Context triple: [Whiteface Mountain, hasEventHistory, 1980 Winter Olympics alpine skiing venue]
-
A.
hasPolicyHistory
Indicates that an entity is associated with a record or sequence of past policies that have applied to it over time.
-
B.
hasHistoricalEvent
chosen
Indicates that a historical event occurred in, is associated with, or is relevant to a particular entity.
-
C.
hasWritingHistory
Indicates that an entity has a recorded history or log of its writing-related actions, changes, or authored content over time.
-
D.
hasFireHistory
Indicates that an entity has experienced one or more fire events in the past.
-
E.
hasHistoricalProcess
Indicates that an entity is associated with, or characterized by, a historical process or sequence of events that unfolded over time.
- 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_69a8870eea088190a38781990812a9bc |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb68a8e608190bc37a85913b3cd44 |
completed | March 7, 2026, 5:24 a.m. |
| PD | Predicate disambiguation | batch_69abaff5dbd48190a9d36ca60de151db |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.