Triple
T11943269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victoria line |
E284229
|
entity |
| Predicate | hasAutomaticTrainOperation |
P55995
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Victoria line, hasAutomaticTrainOperation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAutomaticTrainOperation Context triple: [Victoria line, hasAutomaticTrainOperation, true]
-
A.
hasAutomaticTrainControlCompatibility
chosen
Indicates that an entity is compatible with, or supports integration with, an automatic train control (ATC) system.
-
B.
hasAutomaticFareCollection
Indicates that an entity is equipped with a system that automatically collects fares or payments from users without manual processing.
-
C.
hasRailMode
Indicates that an entity is associated with or supports transportation via rail-based modes (such as trains, trams, or subways).
-
D.
hasPassengerOperations
Indicates that an entity conducts or supports transportation services specifically for carrying passengers.
-
E.
automatedIn
Indicates that an action, process, or operation is performed automatically within or by a specified system, context, or environment.
- 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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9034444488190925a6fa6c856ed08 |
completed | April 10, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3e48e08190b2fee43af4f57323 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.