Triple
T9033780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cascade Lakes Scenic Byway |
E216437
|
entity |
| Predicate | oftenClosedIn |
P12551
|
FINISHED |
| Object | winter |
—
|
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: winter | Statement: [Cascade Lakes Scenic Byway, oftenClosedIn, winter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenClosedIn Context triple: [Cascade Lakes Scenic Byway, oftenClosedIn, winter]
-
A.
openPitClosedIn
Indicates that an open-pit mine or excavation has been closed, decommissioned, or otherwise taken out of active use at a specified time or under specified conditions.
-
B.
closedFor
Indicates that an entity is not available or accessible for use, entry, or operation during a specified time, condition, or reason.
-
C.
closedDuring
chosen
Indicates that an entity is not open or available for use during a specified time period or under certain conditions.
-
D.
alsoOpenOn
Indicates that a place, service, or resource is open or available during an additional specified time or on an additional specified day beyond its primary opening period.
-
E.
closingTime
Indicates the specific time at which a place, service, or activity stops operating or becomes unavailable.
- 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_69ca83d10b608190b2b2f8e0a7faaf14 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6aa248bc8190a55cfc2a5306ab20 |
completed | April 1, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee3597c81908919cf866ae95c24 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:08 p.m.