Triple
T27293344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Westlake Center station |
E688688
|
entity |
| Predicate | openedForTransitTunnel |
P172790
|
FINISHED |
| Object | 1990 |
—
|
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: 1990 | Statement: [Westlake Center station, openedForTransitTunnel, 1990]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedForTransitTunnel Context triple: [Westlake Center station, openedForTransitTunnel, 1990]
-
A.
openedToTransit
Indicates that a route, passage, or connection has been made available or accessible for transit or movement between locations.
-
B.
openedForThroughTraffic
Indicates that a route or segment is available and accessible for vehicles to pass through (not just for local access), allowing continuous through traffic.
-
C.
openedTollSection
Indicates that a toll road segment has been made available for use and is now open to traffic.
-
D.
openedToPassengerTraffic
Indicates that a transportation facility or route began operating and accepting passengers for regular use.
-
E.
openedForTram
Indicates that something (such as a route, track, or facility) is available and in use for tram operations.
- 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_69ef355a96308190a2bed991525fb278 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f6b0d21dd08190a9883ff71c94c71c |
completed | May 3, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6afeaaef88190aefa97e83f8db906 |
completed | May 3, 2026, 2:16 a.m. |
Created at: April 27, 2026, 11:17 a.m.