Triple
T38369113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yahoo! Studios |
E892529
|
entity |
| Predicate | contentTypeProduced |
P145327
|
FINISHED |
| Object | original digital video |
—
|
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: original digital video | Statement: [Yahoo! Studios, contentTypeProduced, original digital video]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contentTypeProduced Context triple: [Yahoo! Studios, contentTypeProduced, original digital video]
-
A.
producedContentType
chosen
Indicates that an entity has created or generated content of a specified type or format.
-
B.
describesContentType
Indicates that one entity specifies or characterizes the type or category of content associated with another entity.
-
C.
broadcastsContentType
Indicates that an entity (such as a broadcaster or channel) transmits or distributes content of a specified type.
-
D.
governsContentType
Indicates that one entity defines or controls the rules, behavior, or handling associated with a particular content type.
-
E.
scriptContentType
Indicates the type or format of the content contained within a script (e.g., language, media, or data type) in relation to that script.
- 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_69f76e47cb4c8190bdd92cd1db59c0c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: May 3, 2026, 4:31 p.m.