Triple
T4264805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disco Demolition Night |
E96797
|
entity |
| Predicate | scheduledAs |
P55062
|
FINISHED |
| Object | doubleheader promotion |
—
|
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: doubleheader promotion | Statement: [Disco Demolition Night, scheduledAs, doubleheader promotion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scheduledAs Context triple: [Disco Demolition Night, scheduledAs, doubleheader promotion]
-
A.
scheduledServiceType
Indicates the type or category of service that has been scheduled between entities (e.g., maintenance, appointment, or delivery).
-
B.
scheduleUS
Indicates that an entity arranges or assigns a time for something specifically within the context of the United States.
-
C.
scheduledInYear
Indicates that an event, activity, or item is planned or set to occur within a specific calendar year.
-
D.
appointedFor
Indicates that an entity has been officially assigned or designated to perform a specific role, task, or function for another entity or purpose.
-
E.
schedule
Indicates that an entity arranges for an event, task, or activity to occur at a specific time or within a defined time frame.
- 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_69b34543f06c8190915ebb1a4574ffa9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34fcad0a881908e1cac0a6da5a321 |
completed | March 12, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69b347f8dcb08190a725c1f7fb5a7466 |
completed | March 12, 2026, 11:10 p.m. |
| PDg | Predicate description generation | batch_69b34e0606488190baadf469a1afc3c2 |
completed | March 12, 2026, 11:36 p.m. |
Created at: March 12, 2026, 11:06 p.m.