Triple
T23898797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central line – Piccadilly line |
E600980
|
entity |
| Predicate | lineOrientationConnected |
P42939
|
FINISHED |
| Object | east–west |
—
|
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: east–west | Statement: [Central line – Piccadilly line, lineOrientationConnected, east–west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineOrientationConnected Context triple: [Central line – Piccadilly line, lineOrientationConnected, east–west]
-
A.
lineOrientation
chosen
Indicates the directional alignment or angle of a line relative to a reference frame or axis.
-
B.
connectedLine
Indicates that two entities are joined by a continuous line or linear connection.
-
C.
lineCorridor
Indicates that one entity is a corridor represented or approximated by a line, typically modeling a narrow passageway or path between areas.
-
D.
lineElement
Indicates a relationship where something functions as, or is identified as, an element or segment of a line within a larger linear structure or representation.
-
E.
connectsCitiesViaLine
Indicates a relationship where a transportation line directly links two or more cities.
- 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_69e295341ac0819080647f2908af793c |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cddca9708190acd3e9edc9b5940b |
completed | April 29, 2026, 9:22 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:25 p.m.