Triple
T11858743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Wizard |
E282105
|
entity |
| Predicate | hasMediaUsage |
P3334
|
FINISHED |
| Object | used by sports broadcasters |
—
|
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: used by sports broadcasters | Statement: [The Wizard, hasMediaUsage, used by sports broadcasters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMediaUsage Context triple: [The Wizard, hasMediaUsage, used by sports broadcasters]
-
A.
hasCommonMedia
Indicates that two entities share at least one media item (such as an image, video, or audio file) in common.
-
B.
usedByMedia
chosen
Indicates that something is employed or utilized by media organizations or media-related channels.
-
C.
hasMedianUse
Indicates that something is associated with a typical or middle level of use within a given range or distribution of usage.
-
D.
hasMediaAppearanceIn
Indicates that an entity appears or is featured as media content within a specified media work, program, or publication.
-
E.
hasLocalMedia
Indicates that an entity is associated with media content that is stored or available locally rather than from a remote source.
- 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a69a099c8190a674db64c50eca5a |
completed | April 10, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69d8a2573dbc8190ab432e8e28fde6cc |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.