Triple
T24016648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myrtle–Wyckoff Avenues |
E594693
|
entity |
| Predicate | hasAdjacentStationOnM |
P154878
|
FINISHED |
| Object | Knickerbocker Avenue |
—
|
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: Knickerbocker Avenue | Statement: [Myrtle–Wyckoff Avenues, hasAdjacentStationOnM, Knickerbocker Avenue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdjacentStationOnM Context triple: [Myrtle–Wyckoff Avenues, hasAdjacentStationOnM, Knickerbocker Avenue]
-
A.
hasAdjacentStationOnAC
Indicates that one station is directly next to another station along the AC line or route.
-
B.
hasAdjacentStationOnU2
Indicates that one station is directly next to another station along the U2 line.
-
C.
hasAdjacentStationSite
Indicates that one station site is located directly next to or bordering another station site.
-
D.
hasAdjacentStationOnLine1
Indicates that one station is directly next to another station along Line 1 in the network.
-
E.
hasAdjacentStationOnIND
Indicates that one station is directly next to another station on the IND (Independent Subway System) line, with no other stations 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_69e288bc8f608190ac4af29f0bd1c744 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d5a3f5a08190b7170270c4fcf080 |
completed | April 29, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
| PDg | Predicate description generation | batch_69f17c28b684819084eea522126463f8 |
completed | April 29, 2026, 3:34 a.m. |
Created at: April 17, 2026, 9:42 p.m.