Triple
T550152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount St. Helens |
E11819
|
entity |
| Predicate | firstRecordedEuropeanSighting |
P10100
|
FINISHED |
| Object | 1792 |
—
|
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: 1792 | Statement: [Mount St. Helens, firstRecordedEuropeanSighting, 1792]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstRecordedEuropeanSighting Context triple: [Mount St. Helens, firstRecordedEuropeanSighting, 1792]
-
A.
firstContactWithEuropeans
chosen
Indicates that this marks the initial recorded encounter or interaction between a group and European people.
-
B.
yearOfEuropeanExploration
Indicates the specific year in which a European exploration of the referenced entity took place.
-
C.
firstEuropeanClaimBy
Indicates that a place or territory was first formally claimed or asserted as possession by a specified European individual, group, or state.
-
D.
firstVoyageEndYear
Indicates the calendar year in which an entity’s first voyage or initial journey was completed or came to an end.
-
E.
firstSettlersArrived
Indicates that the earliest group of settlers reached or came to a particular place or region.
- 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_69a4932941d08190815efd422f0b4ca7 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49901e4e481909a5ed93c21ab37bd |
completed | March 1, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69a494bae210819093c2e0d33a8ca51a |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.