Triple
T25084969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 50th Street |
E628289
|
entity |
| Predicate | notServedByTrain |
P157622
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [50th Street, notServedByTrain, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notServedByTrain Context triple: [50th Street, notServedByTrain, 2]
-
A.
hasRailServiceAt
Indicates that a rail transport service operates at or serves a particular location or facility.
-
B.
notPublicTransit
Indicates that the transportation mode or route is not classified as public transit (e.g., it is private, restricted, or otherwise not available as general public transportation).
-
C.
railwayTypeServed
Indicates the type of railway system or service that a given entity (such as a station, line, or facility) is designed to serve or accommodate.
-
D.
hasRegionalTrainService
Indicates that a location or route is served by regional train services connecting it to nearby areas.
-
E.
servesLocalTrains
Indicates that a station or facility provides service or stops specifically for local (non-express) train routes.
- 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_69e2ff2e73f881909992bf3eda5c25cb |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f461e3bef081908ef1c4d28cfe03e1 |
completed | May 1, 2026, 8:18 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
| PDg | Predicate description generation | batch_69f448fe11f08190bdd53ca7ba2d51e4 |
completed | May 1, 2026, 6:32 a.m. |
Created at: April 18, 2026, 6:23 a.m.