Triple
T29127334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King George station |
E738267
|
entity |
| Predicate | previousStationOnExpoLine |
P194074
|
FINISHED |
| Object | Surrey Central station |
—
|
NE NERFINISHED |
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: Surrey Central station | Statement: [King George station, previousStationOnExpoLine, Surrey Central station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousStationOnExpoLine Context triple: [King George station, previousStationOnExpoLine, Surrey Central station]
-
A.
previousStationOnLine1
Indicates that one station is the immediately preceding station to another station along transit line 1.
-
B.
precedingStationOnOrangeLine
Indicates that one station is immediately before another station along the Orange Line route.
-
C.
previousStationOnLineA
Indicates that one station is immediately before another station along line A in the route order.
-
D.
precedingStationOnBlueLine
Indicates that one station is immediately before another station along the Blue Line route.
-
E.
adjacentStationOnPurpleLineExpress
Indicates that one station is directly next to another station along the Purple Line Express 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_69f07cb29cdc8190afa55444553de60c |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
| PDg | Predicate description generation | batch_69fd5f2903a48190ac4b718bff99c6cf |
completed | May 8, 2026, 3:57 a.m. |
Created at: April 28, 2026, 11:29 a.m.