Triple
T2907512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waterloo & City line |
E63600
|
entity |
| Predicate | isShortestLineOnNetwork |
P8860
|
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: [Waterloo & City line, isShortestLineOnNetwork, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isShortestLineOnNetwork Context triple: [Waterloo & City line, isShortestLineOnNetwork, true]
-
A.
hasEasiestRoute
Indicates that one entity provides or represents the simplest or least difficult route or path to reach another entity or destination.
-
B.
significantlyShortensRouteBetween
Indicates that one entity provides a connection between two others that makes the path or travel distance between them substantially shorter than alternative routes.
-
C.
approximateCircuitLengthMi
Indicates the approximate total length of a circuit, measured in miles.
-
D.
connectedLine
Indicates that two entities are joined by a continuous line or linear connection.
-
E.
routeNetworkCharacteristic
chosen
Indicates a relationship where a specific characteristic or property is attributed to a route within a network.
- 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_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. |
Created at: March 6, 2026, 10:11 p.m.