Triple
T10209869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RTL Group |
E242297
|
entity |
| Predicate | FremantleProduces |
P79723
|
FINISHED |
| Object | entertainment formats |
—
|
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: entertainment formats | Statement: [RTL Group, FremantleProduces, entertainment formats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FremantleProduces Context triple: [RTL Group, FremantleProduces, entertainment formats]
-
A.
westEndProduction
Indicates that one entity is a theatrical production that was staged in London’s West End, associated with the other entity (such as a play, musical, or venue).
-
B.
majorProductionHub
Indicates that a location serves as a primary center where large-scale production or manufacturing activities are concentrated.
-
C.
pilotProducedBy
chosen
Indicates that a pilot episode is created or produced by a specific person, group, or organization.
-
D.
isProducedIn
Indicates that something is created, manufactured, or generated within a particular place, context, or process.
-
E.
producedAs
Indicates that one entity is created, generated, or brought into existence as a result or output of another entity or process.
- 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_69d381ae26c48190985abd0e25ee5d04 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d3aa22071c819095febd18dd607978 |
completed | April 6, 2026, 12:42 p.m. |
| PD | Predicate disambiguation | batch_69d39559e5ac8190b88eca75956b7e6a |
completed | April 6, 2026, 11:13 a.m. |
Created at: April 6, 2026, 11 a.m.