Triple
T22797448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weekly Wipe |
E564287
|
entity |
| Predicate | presentedInStyleOf |
P121907
|
FINISHED |
| Object | voice-over commentary on clips |
—
|
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: voice-over commentary on clips | Statement: [Weekly Wipe, presentedInStyleOf, voice-over commentary on clips]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentedInStyleOf Context triple: [Weekly Wipe, presentedInStyleOf, voice-over commentary on clips]
-
A.
inTheStyleOf
chosen
Indicates that one entity is created, performed, or presented in a manner that imitates or closely resembles the characteristic style of another entity.
-
B.
presentedInFormat
Indicates that something is expressed, delivered, or made available using a particular format or representation.
-
C.
presentedIn
Indicates that something is shown, displayed, or formally introduced within a particular context, medium, event, or setting.
-
D.
exhibitStyle
Indicates that an entity displays, demonstrates, or embodies a particular style or manner of expression.
-
E.
styleInFull
Indicates that something is presented, written, or expressed in its complete, unabbreviated, or fully detailed form.
- 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_69e2458185f88190b0045227ee420411 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17cd9b3c0819096050f43a829ec0d |
completed | April 29, 2026, 3:36 a.m. |
| PD | Predicate disambiguation | batch_69eed2c32e8c8190b73bb9965ed47d64 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:30 p.m.