Triple
T7152866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Livonia Avenue (BMT Canarsie Line) via Junius Street transfer |
E166733
|
entity |
| Predicate | streetConnection |
P36837
|
FINISHED |
| Object | Livonia 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: Livonia Avenue | Statement: [Livonia Avenue (BMT Canarsie Line) via Junius Street transfer, streetConnection, Livonia Avenue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streetConnection Context triple: [Livonia Avenue (BMT Canarsie Line) via Junius Street transfer, streetConnection, Livonia Avenue]
-
A.
streetNetwork
Indicates the layout and connectivity relationships among streets within a geographic area, including how roads intersect, link, and form a navigable network.
-
B.
streetSet
Indicates that a particular street belongs to, or is included within, a specified set or collection of streets.
-
C.
betweenStreets
Indicates that one location is situated between two specified streets, typically along a road segment bounded by those streets.
-
D.
hasConnectingStreet
chosen
Indicates that two locations are linked by a street that directly connects them.
-
E.
streetLocation
Indicates that one entity is located on, along, or at a specific street associated with 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_69c68886779c8190a8e3fbabffe68253 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e7f52c1081908c4fa424d5e965bc |
completed | March 27, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69c6e1caf4e48190b47bb398a3c1554d |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:46 p.m.