Triple
T28096951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East 180th Street station |
E710117
|
entity |
| Predicate | hasRushHourService |
P27955
|
FINISHED |
| Object | 5 train express 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: 5 train express service | Statement: [East 180th Street station, hasRushHourService, 5 train express service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRushHourService Context triple: [East 180th Street station, hasRushHourService, 5 train express service]
-
A.
servedByRushHourService
Indicates that the entity is provided or operated by a rush hour (peak-time) transit service.
-
B.
rushHourServicePattern
Indicates that a service operates according to a specific pattern or schedule that applies only during rush-hour or peak travel times.
-
C.
hasPeakHourService
chosen
Indicates that a service operates or is available during designated peak or high-demand hours.
-
D.
has24HourOperations
Indicates that an entity operates continuously for 24 hours a day without closing.
-
E.
hasWeekdayService
Indicates that a service operates on weekdays (typically Monday through Friday).
- 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_69ef9b70fd108190a875953b2e50ca91 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 27, 2026, 9:02 p.m.