Triple
T1225610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jerome Avenue Line |
E26319
|
entity |
| Predicate | rushHourServicePattern |
P26031
|
FINISHED |
| Object | express in Manhattan, local in the Bronx (4 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: express in Manhattan, local in the Bronx (4 train) | Statement: [Jerome Avenue Line, rushHourServicePattern, express in Manhattan, local in the Bronx (4 train)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rushHourServicePattern Context triple: [Jerome Avenue Line, rushHourServicePattern, express in Manhattan, local in the Bronx (4 train)]
-
A.
offPeakServicePattern
Indicates the service pattern or schedule that applies during off-peak (non-rush-hour) times.
-
B.
typicalTimes
Indicates the usual or characteristic times at which an event, activity, or condition typically occurs.
-
C.
fareControl
Indicates that an entity is responsible for monitoring, enforcing, or managing payment of fares for access to a service or facility.
-
D.
budTime
Indicates the time or period when a bud forms or begins to develop.
-
E.
isOneOfBusiestStopsOn
Indicates that a stop ranks among the most heavily used or frequently served stops on a given route or line.
- 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_69a49484688c8190a1bf285eb396a8b6 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4be39908481908cca21aaf0828415 |
completed | March 1, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69a4bb644af08190ba25905f20adb01a |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bd3140688190ac6e24de157fd61e |
completed | March 1, 2026, 10:26 p.m. |
Created at: March 1, 2026, 7:47 p.m.