Triple
T31747530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Lots |
E810312
|
entity |
| Predicate | railTerminusNearby |
P170255
|
FINISHED |
| Object | New Lots Avenue terminal of the 3 line |
—
|
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: New Lots Avenue terminal of the 3 line | Statement: [New Lots, railTerminusNearby, New Lots Avenue terminal of the 3 line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railTerminusNearby Context triple: [New Lots, railTerminusNearby, New Lots Avenue terminal of the 3 line]
-
A.
nearestRailwayTerminus
Indicates that one location is the closest railway terminus to another specified place.
-
B.
railTerminusFor
Indicates that one location serves as the final or terminal rail station or endpoint for a specified rail line or service.
-
C.
railTerminus
Indicates that a railway line or service ends at a particular station or location, which serves as its final terminus.
-
D.
railConnectionNearby
chosen
Indicates that there is a railway connection located close to the referenced entity or location.
-
E.
nearbyHeritageStation
Indicates that one entity is located close to a heritage (historically or culturally significant) station.
- 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_69f348e233cc819083b6695f70cd75d8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ab4fbb20819086a68b7496bd583b |
completed | May 3, 2026, 1:56 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:27 p.m.