Triple
T9984027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boomtown |
E196520
|
entity |
| Predicate | broadcastStatus |
P91428
|
FINISHED |
| Object | cancelled |
—
|
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: cancelled | Statement: [Boomtown, broadcastStatus, cancelled]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broadcastStatus Context triple: [Boomtown, broadcastStatus, cancelled]
-
A.
broadcastBegan
Indicates that the transmission or airing of a broadcast has started.
-
B.
broadcastService
Indicates that one entity provides or is associated with a broadcast service used to distribute media or information to an audience.
-
C.
broadcastDuring
Indicates that one event or program is broadcast while another specified time period or event is occurring.
-
D.
broadcastType
Indicates the specific mode or category of broadcasting used to transmit content (e.g., live, recorded, streaming, or other broadcast formats) between entities.
-
E.
broadcastStandard
Indicates that one entity uses, supports, or is associated with a particular broadcast transmission standard (such as a TV or radio broadcasting format).
- 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_69ca82efbce081908179b4b9c65096eb |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb8bdc0388190bbbd4bdc5ac3adec |
completed | April 2, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69cd1da07db88190945bcdab3ca82e71 |
completed | April 1, 2026, 1:29 p.m. |
| PDg | Predicate description generation | batch_69cd358386f48190833c862b5b8c04b2 |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:49 p.m.