Triple
T28362541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jay Street–MetroTech |
E718400
|
entity |
| Predicate | adjacentStationOnF |
P174693
|
FINISHED |
| Object | York Street |
—
|
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: York Street | Statement: [Jay Street–MetroTech, adjacentStationOnF, York Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adjacentStationOnF Context triple: [Jay Street–MetroTech, adjacentStationOnF, York Street]
-
A.
adjacentStationOnA
Indicates that one station is directly next to another station along line A in the network.
-
B.
adjacentStationOnL
Indicates that one station is directly next to another station along line L in the network.
-
C.
adjacentStationOnJ
Indicates that one station is directly next to another station along line J in the network.
-
D.
adjacentStationOnC
Indicates that one station is directly next to another station along line C in the network.
-
E.
adjacentStationOnLine
Indicates that one station is directly next to another station along the same transit line, with no other station in between.
- 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_69eff6ed5af48190be4e0adf298223e0 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6c5b7e46081909975b05f7298cc0e |
completed | May 3, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c49069e48190a3486b6254a6645b |
completed | May 3, 2026, 3:44 a.m. |
Created at: April 28, 2026, 12:53 a.m.