Triple
T21463122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Night |
E529523
|
entity |
| Predicate | hasBroadcastStatus |
P144449
|
FINISHED |
| Object | ended series |
—
|
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: ended series | Statement: [First Night, hasBroadcastStatus, ended series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBroadcastStatus Context triple: [First Night, hasBroadcastStatus, ended series]
-
A.
hasBroadcastContent
Indicates that one entity (typically a broadcast or channel) carries, includes, or transmits the specified content.
-
B.
hasBroadcastTime
Indicates that a broadcast (such as a program or transmission) is scheduled or occurs at a specific time.
-
C.
hasBroadcastHistoryWith
Indicates that two entities are connected through a record of past broadcast events involving both of them.
-
D.
hasBroadcastStyle
Indicates that one entity is characterized by, or associated with, a particular manner or style of broadcasting.
-
E.
hasBroadcaster
Indicates that an entity is associated with or transmitted by a particular broadcaster or broadcasting organization.
- 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_69e0c458133481908ae8b41a12c4edec |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9e9efdb188190be79b72e1bd18860 |
completed | April 23, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69e631df1b38819088d3604854e697b4 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e63d2aca38819094d312078feaa436 |
completed | April 20, 2026, 2:50 p.m. |
Created at: April 16, 2026, 6:09 p.m.