Triple
T34490550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danse macabre |
E885454
|
entity |
| Predicate | timeOfActionInProgram |
P57350
|
FINISHED |
| Object | midnight |
—
|
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: midnight | Statement: [Danse macabre, timeOfActionInProgram, midnight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfActionInProgram Context triple: [Danse macabre, timeOfActionInProgram, midnight]
-
A.
hasTimeOfAction
chosen
Indicates that an action is associated with a specific point or interval in time when it occurs.
-
B.
startTimeAsProgrammingBlock
Indicates that one entity’s start time is defined or represented as a programming block associated with that entity or process.
-
C.
executionTiming
Indicates the temporal characteristics or schedule of when an action, process, or event is carried out.
-
D.
timeToControl
Indicates the amount of time required for an entity to gain or establish control over another entity, process, or situation.
-
E.
timeOfDialogue
Indicates the specific time or temporal context at which a dialogue or conversational exchange occurs.
- 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_69f349cafcec8190997b45b3fdc16c27 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
Created at: May 1, 2026, 2:01 a.m.