Triple
T6492306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 168th Street–Washington Heights |
E148069
|
entity |
| Predicate | hasAdjacentStationOn1 |
P41934
|
FINISHED |
| Object | 157th Street |
—
|
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: 157th Street | Statement: [168th Street–Washington Heights, hasAdjacentStationOn1, 157th Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdjacentStationOn1 Context triple: [168th Street–Washington Heights, hasAdjacentStationOn1, 157th Street]
-
A.
hasAdjacentStationOnLine1
chosen
Indicates that one station is directly next to another station along Line 1 in the network.
-
B.
hasAdjacentStationOnIND
Indicates that one station is directly next to another station on the IND (Independent Subway System) line, with no other stations in between.
-
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.
hasAdjacentStationOnU7
Indicates that one station is directly next to another station along the U7 line.
-
E.
hasAdjacentStationOnLine4
Indicates that one station is directly next to another station along transit line 4.
- 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_69c009088f3081909cd467b05919de30 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06a9bf9208190b0957eda06ed3d65 |
completed | March 22, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69c06740bebc81909d9d6956baa2bcb9 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:53 p.m.