Triple
T25398798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mega Millions |
E636364
|
entity |
| Predicate | drawSchedule |
P15179
|
FINISHED |
| Object | Tuesday |
—
|
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: Tuesday | Statement: [Mega Millions, drawSchedule, Tuesday]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drawSchedule Context triple: [Mega Millions, drawSchedule, Tuesday]
-
A.
showSchedule
Indicates that an entity presents or displays a timetable or planned sequence of events for another entity.
-
B.
definesScheduleFor
Indicates that one entity establishes or specifies the schedule according to which another entity operates or is organized.
-
C.
scheduleUS
Indicates that an entity arranges or assigns a time for something specifically within the context of the United States.
-
D.
schedule
chosen
Indicates that an entity arranges for an event, task, or activity to occur at a specific time or within a defined time frame.
-
E.
relatedSchedule
Indicates a relationship where one schedule is associated with, linked to, or derived from another schedule.
- 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_69e75db263888190b77fff9e2827b9a2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 21, 2026, 1:50 p.m.