Triple
T26304918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L line |
E661653
|
entity |
| Predicate | CBTCStatus |
P112656
|
FINISHED |
| Object | fully equipped |
—
|
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: fully equipped | Statement: [L line, CBTCStatus, fully equipped]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CBTCStatus Context triple: [L line, CBTCStatus, fully equipped]
-
A.
railStatus
Indicates the current operational condition or state of a rail-related entity (such as a track, line, or service) within the system.
-
B.
hasAutomaticTrainControlCompatibility
Indicates that an entity is compatible with, or supports integration with, an automatic train control (ATC) system.
-
C.
followingTrainStatus
Indicates that one entity is tracking or monitoring the current operational status or progress of a train.
-
D.
statusOfTrain7
Indicates the current operational status or condition of train number 7 in relation to its schedule or service.
-
E.
hasAutomaticTrainControl
chosen
Indicates that an entity is equipped with or uses an automatic train control system for managing train operations.
- 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_69ee812dacfc81908484aade9120fba9 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60ee22a908190a62640e48c2e7659 |
completed | May 2, 2026, 2:49 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 10:18 p.m.