Triple
T11439233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ozone Park–Lefferts Boulevard |
E271096
|
entity |
| Predicate | hasServiceTime |
P99305
|
FINISHED |
| Object | 24-hour service by A 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: 24-hour service by A train | Statement: [Ozone Park–Lefferts Boulevard, hasServiceTime, 24-hour service by A train]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasServiceTime Context triple: [Ozone Park–Lefferts Boulevard, hasServiceTime, 24-hour service by A train]
-
A.
hasServiceTo
Indicates that one entity provides, offers, or operates a service for or directed toward another entity.
-
B.
servedTimeAt
Indicates the specific time period during which an entity was served or received service at a particular place or context.
-
C.
hasTimeStart
Indicates that an event, process, or state begins at a specific point in time.
-
D.
hasSupportService
Indicates that one entity provides or is associated with a support-related service for another entity.
-
E.
hasTimeOfAction
Indicates that an action is associated with a specific point or interval in time when it occurs.
- 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_69d6aadeef688190874bcecd88b3dd9b |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d80888190c8190b6365550ffe4931c |
completed | April 9, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69d7e7162b288190a0bfb89f7eb747c7 |
completed | April 9, 2026, 5:51 p.m. |
| PDg | Predicate description generation | batch_69d800115af08190bba53dd3ff561ca1 |
completed | April 9, 2026, 7:37 p.m. |
Created at: April 8, 2026, 9:35 p.m.