Triple
T5550981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Primetime Emmy Award for Outstanding Television Movie |
E145523
|
entity |
| Predicate | ceremonySchedule |
P14854
|
FINISHED |
| Object | held annually in late summer |
—
|
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: held annually in late summer | Statement: [Primetime Emmy Award for Outstanding Television Movie, ceremonySchedule, held annually in late summer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceremonySchedule Context triple: [Primetime Emmy Award for Outstanding Television Movie, ceremonySchedule, held annually in late summer]
-
A.
ceremonyTiming
chosen
Indicates the temporal relationship specifying when a ceremony occurs or is scheduled to occur.
-
B.
ceremonyHeld
Indicates that a formal ceremony or ritual event has taken place at a particular time and/or location.
-
C.
ceremonyHeldOn
Indicates that a specific ceremony took place on a particular date or day.
-
D.
ceremonyIncludes
Indicates that a particular ceremony contains, involves, or encompasses a specified component, activity, or element as part of its structure or proceedings.
-
E.
ceremonyState
Indicates the current status or phase of a ceremony within its overall lifecycle.
- 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_69c008fb879c81909f5bfa56fadc1d46 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01fe3e7788190aa5361b083197c17 |
completed | March 22, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69c01b0e72f08190bf705d8fe1639401 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:35 p.m.