Triple
T26785471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 31 Nights of Halloween |
E670366
|
entity |
| Predicate | secondaryBroadcastTime |
P66213
|
FINISHED |
| Object | weekend afternoons |
—
|
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: weekend afternoons | Statement: [31 Nights of Halloween, secondaryBroadcastTime, weekend afternoons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryBroadcastTime Context triple: [31 Nights of Halloween, secondaryBroadcastTime, weekend afternoons]
-
A.
hasBroadcastTime
chosen
Indicates that a broadcast (such as a program or transmission) is scheduled or occurs at a specific time.
-
B.
originalBroadcastPeriod
Indicates the time span during which a work was first broadcast or aired in its original run.
-
C.
laterBroadcastBy
Indicates that a broadcast or airing of some content occurred at a later time on the specified broadcaster or channel.
-
D.
firstBroadcastTime
Indicates the date and time at which something (typically a program or content) was first broadcast.
-
E.
rebroadcastDelay
Indicates the time interval that must pass before an action, message, or signal is transmitted again after its initial broadcast.
- 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_69eeb31d45f8819089f52ebdbc556218 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 27, 2026, 4:12 a.m.