Triple
T27656258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clark Street |
E697000
|
entity |
| Predicate | subwayStationServedBy |
P18378
|
FINISHED |
| Object | IRT Broadway–Seventh Avenue 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: IRT Broadway–Seventh Avenue Line | Statement: [Clark Street, subwayStationServedBy, IRT Broadway–Seventh Avenue Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subwayStationServedBy Context triple: [Clark Street, subwayStationServedBy, IRT Broadway–Seventh Avenue Line]
-
A.
subwayStation
Indicates that one entity is a subway station associated with, located in, or serving the other entity.
-
B.
subwayServices
Indicates that one entity provides or operates subway transportation services for another entity or area.
-
C.
subwayLine
chosen
Indicates that there is a subway line connection or service relationship between the referenced entities.
-
D.
transportationServedBy
Indicates that a transportation facility, route, or area is provided service or coverage by a specific transportation provider or mode.
-
E.
railInfrastructureServed
Indicates that a rail infrastructure facility or segment is served, accessed, or operated by a particular service, operator, or network.
- 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_69ef590abd3c8190834d0193bde12007 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6359e3d3c81909814e2f0a7fb0ea9 |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 2:34 p.m.