Triple
T6889617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christof |
E159010
|
entity |
| Predicate | showBroadcastTo |
P56798
|
FINISHED |
| Object | global television audience (in-universe) |
—
|
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: global television audience (in-universe) | Statement: [Christof, showBroadcastTo, global television audience (in-universe)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: showBroadcastTo Context triple: [Christof, showBroadcastTo, global television audience (in-universe)]
-
A.
broadcastsTo
chosen
Indicates that one entity transmits or disseminates information, signals, or content to another entity or group of entities.
-
B.
broadcastPlatform
Indicates the platform or channel through which content is broadcast or transmitted.
-
C.
broadcastsIn
Indicates that one entity transmits or airs content within a particular medium, channel, location, or time frame.
-
D.
showsThat
Indicates that one entity demonstrates, proves, or provides evidence for the truth or validity of another.
-
E.
broadcastFor
Indicates that one entity transmits or disseminates content, information, or a signal on behalf of, or in service of, another entity.
- 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_69c6883568c8819081db6407e892cccc |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d9117c84819093dad7b765337b63 |
completed | March 27, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b53e9881909ec298daa9f1913b |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:23 p.m.