Triple
T9702941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GCM |
E234822
|
entity |
| Predicate | openedForFullService |
P990
|
FINISHED |
| Object | February 27, 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: February 27, 2023 | Statement: [GCM, openedForFullService, February 27, 2023]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedForFullService Context triple: [GCM, openedForFullService, February 27, 2023]
-
A.
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.
-
B.
openedForCommercialService
Indicates that something (such as a facility, route, or service) began operating and became available for regular commercial use.
-
C.
openedForServiceOnLine
Indicates that an entity (such as a facility or station) began operating and providing service on a specified transit or service line.
-
D.
openedForUse
chosen
Indicates that something has been made accessible and available for its intended operation or use.
-
E.
openedForCurrentUse
Indicates that an entity has been opened and is currently available for its intended use or operation.
- 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_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. |
Created at: March 30, 2026, 8:18 p.m.