Triple
T28202804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banijay Rights |
E716932
|
entity |
| Predicate | parentGroupActivity |
P175989
|
FINISHED |
| Object | television production |
—
|
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: television production | Statement: [Banijay Rights, parentGroupActivity, television production]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentGroupActivity Context triple: [Banijay Rights, parentGroupActivity, television production]
-
A.
parentAct
Indicates that one entity performs an action in the role of a parent toward another entity, typically involving caregiving, guidance, or parental responsibility.
-
B.
parentService
Indicates that one service functions as the higher-level or owning service in relation to another, which depends on or is derived from it.
-
C.
parentStudio
Indicates that one studio serves as the parent or owning studio of another studio.
-
D.
parentMission
Indicates that one mission serves as the direct parent or higher-level mission from which another mission is derived or organized.
-
E.
parentShow
Indicates that one show is the primary or originating show from which another show is derived, related, or subordinate.
- F. None of above. chosen
Provenance (4 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_69efd6b826908190857e6e7dad74ed93 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6db3606808190a80c6e9f5da5b33e |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6db1bc348819097c844f76e2fa4fe |
completed | May 3, 2026, 5:20 a.m. |
Created at: April 27, 2026, 10:33 p.m.