Triple
T35616596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avenue B |
E1029185
|
entity |
| Predicate | hasNearbySubway |
P169742
|
FINISHED |
| Object | First Avenue station (L train) |
—
|
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: First Avenue station (L train) | Statement: [Avenue B, hasNearbySubway, First Avenue station (L train)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbySubway Context triple: [Avenue B, hasNearbySubway, First Avenue station (L train)]
-
A.
hasNearbyOvergroundLine
Indicates that one entity is located close to an above-ground railway or transit line associated with the other entity.
-
B.
hasNearbyUndergroundStationEntrance
Indicates that one entity is located close to an entrance of an underground (subway/metro) station.
-
C.
subwayServiceAtNearbyStation
chosen
Indicates that there is subway service available at a station located near the referenced place or entity.
-
D.
hasSubway
Indicates that a place is served by or contains a subway (metro) system.
-
E.
subwayStation
Indicates that one entity is a subway station associated with, located in, or serving the other entity.
- 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_69f76e0709408190bbe322bf1707ef6b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a00233e2170819084bee0c8f74cc1a4 |
completed | May 10, 2026, 6:18 a.m. |
| PD | Predicate disambiguation | batch_6a0022943fd08190b73007f080d5971d |
completed | May 10, 2026, 6:15 a.m. |
Created at: May 3, 2026, 4:05 p.m.