Triple
T8307294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oval Underground Station |
E194493
|
entity |
| Predicate | liesBetweenStationOnLine |
P66204
|
FINISHED |
| Object | Stockwell on Northern line |
—
|
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: Stockwell on Northern line | Statement: [Oval Underground Station, liesBetweenStationOnLine, Stockwell on Northern line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liesBetweenStationOnLine Context triple: [Oval Underground Station, liesBetweenStationOnLine, Stockwell on Northern line]
-
A.
isBetweenStationsOnLine
chosen
Indicates that something is located or occurs between two stations along the same transit line.
-
B.
hasAdjacentStationOnLine1
Indicates that one station is directly next to another station along Line 1 in the network.
-
C.
hasAdjacentStationOnLine12
Indicates that one station is directly next to another station along transit line 12, with no other stations in between on that line.
-
D.
hasAdjacentStationOnLine50
Indicates that one station is directly next to another station along transit line 50.
-
E.
isJunctionOnLine
Indicates that a particular junction lies on, or is part of, a specified line.
- 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_69ca82e613e88190bf8139669bbd0d53 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f2a86bc81909749c40c640aa9f8 |
completed | March 31, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69cb70bb3a708190bc705222092da614 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:54 p.m.