Triple
T10615060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingsbridge Heights |
E276095
|
entity |
| Predicate | subwayServiceNearby |
P33877
|
FINISHED |
| Object | 1 train |
—
|
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: 1 train | Statement: [Kingsbridge Heights, subwayServiceNearby, 1 train]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subwayServiceNearby Context triple: [Kingsbridge Heights, subwayServiceNearby, 1 train]
-
A.
subwayStationsApprox
Indicates that one subway station is approximately located near or corresponds to another subway station, allowing for minor differences in position or naming.
-
B.
subwayStation
Indicates that one entity is a subway station associated with, located in, or serving the other entity.
-
C.
nearMetroStation
chosen
Indicates that one entity is located close to or within a short walking distance of a metro (subway) station.
-
D.
subwayServices
Indicates that one entity provides or operates subway transportation services for another entity or area.
-
E.
nearestSuburbanRailwayStation
Indicates the relationship where a given place is associated with the suburban railway station that is geographically closest to it.
- 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_69d6aaf948d88190806cc3a8c47a3fb2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d6df5da6808190bd4cb486431dc42c |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7a223c8190854409d76368f3e8 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 7:33 p.m.