Triple
T21181763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daystar Productions |
E521967
|
entity |
| Predicate | producedForMedium |
P71054
|
FINISHED |
| Object | broadcast television |
—
|
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: broadcast television | Statement: [Daystar Productions, producedForMedium, broadcast television]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: producedForMedium Context triple: [Daystar Productions, producedForMedium, broadcast television]
-
A.
mediumOfProduction
Indicates the method, material, or technology used to create or produce something.
-
B.
createdForMedium
chosen
Indicates that something was created specifically for use, display, or performance in a particular medium or format.
-
C.
producesFor
Indicates that one entity creates, manufactures, or generates something specifically intended for another entity’s use, benefit, or distribution.
-
D.
representsMedium
Indicates that one entity serves as the medium, channel, or means through which another entity is expressed, communicated, or realized.
-
E.
producedAs
Indicates that one entity is created, generated, or brought into existence as a result or output of another entity or process.
- 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_69e0b50ef1d48190b063aa342667df22 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7301eb3248190b9f6fc1586651fec |
completed | April 21, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69e5f6027c248190a170a36612bd337e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:01 p.m.