Triple
T9702940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GCM |
E234822
|
entity |
| Predicate | openedForShuttleService |
P90773
|
FINISHED |
| Object | January 25, 2023 |
—
|
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: January 25, 2023 | Statement: [GCM, openedForShuttleService, January 25, 2023]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedForShuttleService Context triple: [GCM, openedForShuttleService, January 25, 2023]
-
A.
openedToTransit
Indicates that a route, passage, or connection has been made available or accessible for transit or movement between locations.
-
B.
openedForThroughService
Indicates that an entity has been made accessible or available specifically for use via a through-service connection or route, rather than as a standalone endpoint.
-
C.
openedAsMetraService
Indicates that a transportation facility or line began operating specifically as part of the Metra commuter rail service.
-
D.
openedAsTransitStation
Indicates that an entity began operation specifically as a transit station at the time it was opened.
-
E.
hasShuttleLine
Indicates that there is a shuttle service or route operating between the related entities.
- 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_69ca84cc78808190a56f3402b7c139a7 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9d73a0148190ad4178fd462cdd9c |
completed | April 1, 2026, 10:34 p.m. |
| PD | Predicate disambiguation | batch_69cd03b641408190942464eaf174c6b5 |
completed | April 1, 2026, 11:38 a.m. |
| PDg | Predicate description generation | batch_69cd081a9c5c819093439be7e802ff85 |
completed | April 1, 2026, 11:57 a.m. |
Created at: March 30, 2026, 8:18 p.m.