Triple
T3192487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York City Subway 4 line |
E66855
|
entity |
| Predicate | nightServiceType |
P9557
|
FINISHED |
| Object | local in Manhattan |
—
|
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: local in Manhattan | Statement: [New York City Subway 4 line, nightServiceType, local in Manhattan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nightServiceType Context triple: [New York City Subway 4 line, nightServiceType, local in Manhattan]
-
A.
nightService
Indicates that a service operates or is available during nighttime hours.
-
B.
nightServicePattern
chosen
Indicates that a service or operation follows a specific pattern or schedule that applies only during nighttime hours.
-
C.
nightServiceRoute
Indicates that a transportation route operates specifically during nighttime or late-night hours.
-
D.
associatedNightTiming
Indicates a relationship where an event, action, or condition is linked specifically to a time period occurring during the night.
-
E.
nightlifePattern
Indicates a recurring way entities engage in or are associated with nightlife activities, such as typical behaviors, schedules, or participation patterns during night hours.
- 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_69ad8588ba18819086a10951c32ecb80 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada6e8e4b48190bc7c6443fc6da900 |
completed | March 8, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69ad9e04290481909092ddfbe6fdaabc |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:07 p.m.