Triple
T4249967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Susten Pass |
E95824
|
entity |
| Predicate | roadOpensIn |
P43960
|
FINISHED |
| Object | June |
—
|
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: June | Statement: [Susten Pass, roadOpensIn, June]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadOpensIn Context triple: [Susten Pass, roadOpensIn, June]
-
A.
openingTime
chosen
Indicates the time at which a place, service, or event begins operating or becomes accessible.
-
B.
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.
-
C.
openingHoursCharacteristic
Indicates a relationship that specifies particular attributes or features of an entity’s opening hours, such as patterns, exceptions, or special conditions.
-
D.
roofOpeningTime
Indicates the time at which a roof (typically movable or retractable) is opened.
-
E.
travelTimeAfterOpening
Indicates the amount of time required to travel between specified points, measured from the moment a referenced entity (such as a facility or route) becomes open or available.
- 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_69b3453f759881909b91f01a1e82c036 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e9f11008190a0021e0ad730a79d |
completed | March 12, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69b347f73e008190a908a48ef389945a |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:06 p.m.