Triple
T4205338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kelvinbridge subway station |
E86169
|
entity |
| Predicate | isOnCircleLine |
P51801
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Kelvinbridge subway station, isOnCircleLine, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnCircleLine Context triple: [Kelvinbridge subway station, isOnCircleLine, yes]
-
A.
isOnCircularRoute
chosen
Indicates that an entity follows or belongs to a route that forms a closed loop, starting and ending at the same point.
-
B.
adjacentStationOnCircleLine
Indicates that one station is directly next to another station along the Circle Line, with no other stations in between.
-
C.
isOnEastWestTrunkLine
Indicates that something is located on, or directly aligned with, a primary east–west transportation or utility trunk line.
-
D.
appliesToTransitLine
Indicates that a rule, condition, or characteristic is specifically associated with and relevant to a particular transit line.
-
E.
hasNearbyStateLine
Indicates that one location is situated close to the boundary line of a neighboring state.
- 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_69aed93b89f48190a31f6d57c760e42f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af0382eafc8190946bf45bf28095dd |
completed | March 9, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69af0196716c81908b99193690630a29 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:49 p.m.