Triple
T10209868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RTL Group |
E242297
|
entity |
| Predicate | FremantleSpecialization |
P92719
|
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: [RTL Group, FremantleSpecialization, television production]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FremantleSpecialization Context triple: [RTL Group, FremantleSpecialization, television production]
-
A.
positionSpecialization
Indicates that one position is a more specialized or focused variant of another, broader position.
-
B.
uniformSpecialty
Indicates that multiple entities share the same specific specialty, expertise, or area of focus.
-
C.
fleetCommander (British)
Indicates that the subject serves as the fleet commander for the British naval forces.
-
D.
hasSpecialist
Indicates that one entity is associated with or assigned to a specialist entity that provides expert support, service, or oversight for it.
-
E.
branchOfServiceModelledOn
Indicates that one branch of service is modeled, structured, or designed based on another branch of service.
- 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_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. |
| PDg | Predicate description generation | batch_69d3aa208c248190a0fb186b106389f3 |
completed | April 6, 2026, 12:42 p.m. |
Created at: April 6, 2026, 11 a.m.