Triple
T5263421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vinsanity |
E118880
|
entity |
| Predicate | mediaUsedBy |
P3334
|
FINISHED |
| Object | 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: sports broadcasters | Statement: [Vinsanity, mediaUsedBy, sports broadcasters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mediaUsedBy Context triple: [Vinsanity, mediaUsedBy, sports broadcasters]
-
A.
mediaUse
Indicates that an entity makes use of, consumes, or engages with a particular medium or media resource.
-
B.
mediaExposure
Indicates the extent to which an entity is subjected to or receives attention from media channels such as television, radio, print, or online platforms.
-
C.
usedByMedia
chosen
Indicates that something is employed or utilized by media organizations or media-related channels.
-
D.
mediaDependentInterface
Indicates that one interface or interaction is contingent on, or varies according to, the characteristics or type of the media involved.
-
E.
mediaName
Indicates the name or title assigned to a media item (such as a work, file, or publication) in the relationship.
- 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_69bd446a42c88190b7ecbef006561d55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7bd2eff4819087420e30c140e6f6 |
completed | March 20, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69bd77c55224819096c0bcfcfae79bd3 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:51 p.m.