Triple
T38096618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington State Route 706 |
E951260
|
entity |
| Predicate | terminusInside |
P388
|
FINISHED |
| Object | Mount Rainier National Park |
—
|
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 National Park | Statement: [Washington State Route 706, terminusInside, Mount Rainier National Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusInside Context triple: [Washington State Route 706, terminusInside, Mount Rainier National Park]
-
A.
terminusInland
Indicates that something ends, concludes, or has its final point within an inland area rather than at a coast or shoreline.
-
B.
terminus
chosen
Indicates that one entity serves as the final endpoint or stopping place for another entity’s movement, route, or process.
-
C.
terminusRegion
Indicates the region or area where something (such as a route, line, or process) ends or reaches its final point.
-
D.
terminusTowards
Indicates that one entity serves as the endpoint or directional terminus oriented toward another entity.
-
E.
terminusUpper
Indicates that one entity serves as the upper or final endpoint (terminus) of another entity, such as a route, segment, or ordered structure.
- 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_69f76f04960c8190a83f14ae4c67f5bc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:21 p.m.