Triple
T23921918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Bernardino Pass |
E602238
|
entity |
| Predicate | tunnelOpenInWinter |
P154374
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [San Bernardino Pass, tunnelOpenInWinter, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tunnelOpenInWinter Context triple: [San Bernardino Pass, tunnelOpenInWinter, yes]
-
A.
secondTunnelOpened
Indicates that a second tunnel has been opened and is now available for use in addition to an existing tunnel.
-
B.
tunnelOpened
Indicates that a tunnel has been created or made accessible, establishing an open passage between two locations or systems.
-
C.
openedAsWinterland
Indicates that one entity was opened or inaugurated under the name "Winterland" (i.e., it began operation as Winterland).
-
D.
tunnels
Indicates that one entity passes through, under, or within another entity via a tunnel-like passage or structure.
-
E.
canOperateInTunnels
Indicates that the subject has the capability or is permitted to function or be used within tunnel environments.
- 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_69e2953b928c819095395fa87baca583 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cf19e34481909909bda3f52cabb3 |
completed | April 29, 2026, 9:27 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 8:41 p.m.