Triple
T2857338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 161st Street–Yankee Stadium station |
E63233
|
entity |
| Predicate | servesBoroughFunction |
P9555
|
FINISHED |
| Object | major Bronx transit hub |
—
|
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: major Bronx transit hub | Statement: [161st Street–Yankee Stadium station, servesBoroughFunction, major Bronx transit hub]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesBoroughFunction Context triple: [161st Street–Yankee Stadium station, servesBoroughFunction, major Bronx transit hub]
-
A.
hasBoroughCouncil
Indicates that an administrative area is governed or overseen by a specific borough council.
-
B.
boroughServed
chosen
Indicates that a given entity (such as a facility, service, or route) serves or provides coverage to a specific borough.
-
C.
hasCivicFunction
Indicates that an entity performs, is responsible for, or is associated with an official public or civic role, duty, or service.
-
D.
isBoroughSeatOf
Indicates that a place serves as the administrative center or seat of government for a specific borough.
-
E.
servedDistrict
Indicates that an entity has provided official service or representation to a particular district.
- 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_69ab4c41e8c08190a9e8f5249cc12610 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf881bbc81908987317b88b405d0 |
completed | March 7, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69abdd10aef88190b750aae07e7df4dc |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.