Triple
T5481811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Northern Railway |
E123481
|
entity |
| Predicate | enteredGlacierNationalPark |
P64278
|
FINISHED |
| Object | east side |
—
|
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: east side | Statement: [Great Northern Railway, enteredGlacierNationalPark, east side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredGlacierNationalPark Context triple: [Great Northern Railway, enteredGlacierNationalPark, east side]
-
A.
withinNationalPark
Indicates that one entity is located inside the geographic boundaries of a national park designated by another entity.
-
B.
hasGlacierAccess
Indicates that an entity has direct access to, or is reachable from, a glacier (e.g., via paths, routes, or physical adjacency).
-
C.
establishedAsPark
Indicates that an area or site has been officially designated and recognized as a park.
-
D.
containsNaturalPark
Indicates that one entity geographically includes or encompasses a natural park within its boundaries.
-
E.
isFirstNationalParkIn
Indicates that a given national park holds the distinction of being the first established national park within a specified country or region.
- 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd93e5d0f08190a6cc9fc408b7c5bb |
completed | March 20, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69bd91a73b148190a865243536a4fe76 |
completed | March 20, 2026, 6:27 p.m. |
| PDg | Predicate description generation | batch_69bd93e4d2d081908eb75ee22fe72824 |
completed | March 20, 2026, 6:37 p.m. |
Created at: March 20, 2026, 2:09 p.m.