Triple
T2907492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waterloo & City line |
E63600
|
entity |
| Predicate | transferredToLondonUnderground |
P42669
|
FINISHED |
| Object | 1994-04-01 |
—
|
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: 1994-04-01 | Statement: [Waterloo & City line, transferredToLondonUnderground, 1994-04-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transferredToLondonUnderground Context triple: [Waterloo & City line, transferredToLondonUnderground, 1994-04-01]
-
A.
operatedAsUndergroundMovementUntil
Indicates that an organization or group functioned covertly as an underground movement up to a specified point in time.
-
B.
openedAsSubway
Indicates that a transportation facility or line originally began operation specifically as a subway service.
-
C.
nearUndergroundLine
Indicates that one entity is located close in distance to an underground (subway/metro) line.
-
D.
subwayStation
Indicates that one entity is a subway station associated with, located in, or serving the other entity.
-
E.
primaryLondonTerminal
Indicates that a given station serves as the main London terminal for a particular rail service or route.
- 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_69ab4c44ab448190b9411324e8a1fc1d |
completed | March 6, 2026, 9:51 p.m. |
| NER | Named-entity recognition | batch_69abe0d0628c81909680af2f0db2ecae |
completed | March 7, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69abdd19bac881908f047d616aca8438 |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abdd96670c8190b727f9ac27dadf67 |
completed | March 7, 2026, 8:11 a.m. |
Created at: March 6, 2026, 10:11 p.m.