Triple
T19578748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moffat Tunnel |
E489928
|
entity |
| Predicate | hasWestPortalIn |
P1974
|
FINISHED |
| Object | near Winter Park, Colorado |
—
|
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: near Winter Park, Colorado | Statement: [Moffat Tunnel, hasWestPortalIn, near Winter Park, Colorado]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWestPortalIn Context triple: [Moffat Tunnel, hasWestPortalIn, near Winter Park, Colorado]
-
A.
hasPortal
Indicates that one entity possesses or provides access to a portal connecting to another location or entity.
-
B.
hasWestFace
Indicates that an entity has a side, surface, or face that is oriented toward the west.
-
C.
hasEntranceOn
chosen
Indicates that one entity’s entrance or access point is located on or faces a specified side, boundary, or feature of another entity.
-
D.
hasMainPortal
Indicates that one entity serves as the primary or main portal (entry point or access interface) for another entity.
-
E.
hasEntrance
Indicates that one entity possesses or provides an entry point or access way to another entity or space.
- 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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6402693d88190a828c0e136895783 |
completed | April 20, 2026, 3:03 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:42 p.m.