Triple
T12467963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woodside–61st Street transit hub |
E297974
|
entity |
| Predicate | subwayServicePattern |
P18378
|
FINISHED |
| Object | 7 local service |
—
|
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: 7 local service | Statement: [Woodside–61st Street transit hub, subwayServicePattern, 7 local service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subwayServicePattern Context triple: [Woodside–61st Street transit hub, subwayServicePattern, 7 local service]
-
A.
subwayServices
Indicates that one entity provides or operates subway transportation services for another entity or area.
-
B.
subwayOperation
Indicates the operation or running of a subway system, relating transit services to the times, routes, or conditions under which subway trains are in service.
-
C.
subwaySeries
Indicates a sports matchup or series played between two teams from the same metropolitan area, especially within the same city.
-
D.
subwayStation
Indicates that one entity is a subway station associated with, located in, or serving the other entity.
-
E.
subwayLine
chosen
Indicates that there is a subway line connection or service relationship between the referenced entities.
- 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_69d6ada270808190b1a2b2e7b02bb426 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e626dbc8190ac7dcdb542ba9b0c |
completed | April 10, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69d94d3f701c81909dd0e00251ac8553 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:56 p.m.