Triple
T11614398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | One for My Baby (and One More for the Road) |
E275466
|
entity |
| Predicate | timeOfDaySetting |
P6019
|
FINISHED |
| Object | late night |
—
|
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: late night | Statement: [One for My Baby (and One More for the Road), timeOfDaySetting, late night]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfDaySetting Context triple: [One for My Baby (and One More for the Road), timeOfDaySetting, late night]
-
A.
timeOfSetting
Indicates the specific time at which an event, object, or phenomenon is set, scheduled, or takes place.
-
B.
dayBeginsAt
Indicates the specific time at which a given day starts.
-
C.
timeOfDayCoverage
Indicates the specific portion or range of the day during which an activity, service, or condition is in effect or applicable.
-
D.
dayPattern
Indicates the recurring schedule or configuration of days on which an event, action, or condition occurs.
-
E.
hasTimeOfDay
chosen
Indicates that a situation, event, or state occurs during, or is associated with, a specific part of the day (e.g., morning, afternoon, evening, night).
- 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_69d6aaf84b548190ac072e4fb89ae18f |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a044a3088190b92f4674c2d0b443 |
completed | April 10, 2026, 7:01 a.m. |
| PD | Predicate disambiguation | batch_69d85dd6503c819081f9045e9d5c4f3f |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.