Triple
T25344810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ingraham Flats |
E635515
|
entity |
| Predicate | onStandardRouteOf |
P158225
|
FINISHED |
| Object | Mount Rainier summit |
—
|
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: Mount Rainier summit | Statement: [Ingraham Flats, onStandardRouteOf, Mount Rainier summit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onStandardRouteOf Context triple: [Ingraham Flats, onStandardRouteOf, Mount Rainier summit]
-
A.
isStandardRouteOn
Indicates that a particular route is the default or officially designated path used on a given transportation line or service.
-
B.
routeOf
Indicates that one entity is the path, course, or trajectory taken or followed by another entity (such as a vehicle, shipment, or signal).
-
C.
standardRouteStartsFrom
Indicates that a standard or predefined route has its starting point at a specified location or entity.
-
D.
mayRouteTo
Indicates that one entity is permitted or able to direct, forward, or transfer something (such as data, traffic, or requests) to another entity.
-
E.
followsRouteOf
Indicates that one entity travels along the same path or route that another entity takes or has taken.
- 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_69e75a9ac5d881909387ed766e20cd47 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f498ba4384819094bb42f61fac6bf6 |
completed | May 1, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
| PDg | Predicate description generation | batch_69f464ae42e88190b3549fdf4e0b425e |
completed | May 1, 2026, 8:30 a.m. |
Created at: April 21, 2026, 1:34 p.m.