Triple
T22818771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 103rd Street station (IRT Lexington Avenue Line) |
E565169
|
entity |
| Predicate | servedByDay |
P27954
|
FINISHED |
| Object | 6 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: 6 train | Statement: [103rd Street station (IRT Lexington Avenue Line), servedByDay, 6 train]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedByDay Context triple: [103rd Street station (IRT Lexington Avenue Line), servedByDay, 6 train]
-
A.
servedDuring
Indicates that one entity held a role, position, or performed a function within the time period defined by another entity.
-
B.
servedBetween
Indicates that an entity provided service or operated during a time interval bounded by two specified temporal points.
-
C.
servedByTimePeriod
Indicates that a service, event, or activity occurs or is provided during a specified time period.
-
D.
servedUntil
Indicates the ending time or date up to which an entity held a position, role, or service.
-
E.
hasDailyService
chosen
Indicates that a service or operation occurs every day on a regular, scheduled basis.
- 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_69e2458426188190b58b8ab4844fe420 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17dce762c8190934fb921f942c9fd |
completed | April 29, 2026, 3:41 a.m. |
| PD | Predicate disambiguation | batch_69eed2d117088190acbfe130d84f8627 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:33 p.m.