Triple
T33123682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cignal TV |
E847665
|
entity |
| Predicate | contentRole |
P20270
|
FINISHED |
| Object | content distributor |
—
|
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: content distributor | Statement: [Cignal TV, contentRole, content distributor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contentRole Context triple: [Cignal TV, contentRole, content distributor]
-
A.
roleInText
Indicates that an entity participates in a text with a specific function or capacity (e.g., author, editor, character).
-
B.
roleInMetadata
Indicates that an entity serves a specific function or position within a metadata record or metadata structure.
-
C.
themeRole
Indicates that an entity is the primary participant undergoing or affected by the action or event expressed by a predicate.
-
D.
mediaRole
chosen
Indicates the specific function, capacity, or position an entity holds in relation to a media item (such as creator, editor, performer, or distributor).
-
E.
roleInVox
Indicates that an entity holds a specific role or function within a Vox-related context, such as a project, system, or organization named or described as "Vox."
- 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_69f349588f088190b7c9588860f72033 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 1, 2026, 1:27 a.m.