Triple
T3440117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ITV Digital |
E72543
|
entity |
| Predicate | contractValue |
P48293
|
FINISHED |
| Object | 315 million pounds sterling |
—
|
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: 315 million pounds sterling | Statement: [ITV Digital, contractValue, 315 million pounds sterling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contractValue Context triple: [ITV Digital, contractValue, 315 million pounds sterling]
-
A.
contractUnit
Indicates that one entity serves as a contractual unit or party within a contract relationship involving another entity.
-
B.
contractFeature
Indicates that one entity is a feature, term, or provision that is included in or associated with a particular contract.
-
C.
typeOfContract
Indicates the specific kind or category of contractual agreement that applies between the related entities.
-
D.
notableContract
Indicates that there exists a contract or agreement between entities that is of particular significance, prominence, or public interest.
-
E.
agreementSigned
Indicates that a formal agreement or contract has been officially signed and accepted by the involved parties.
- 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_69ad85af50288190a854b76653deee6f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb9f833e88190b5e813f115621a5f |
completed | March 8, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69adae00ad588190bef24373b58a2e1a |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adaed74ecc8190b74dc70ab59a3e1c |
completed | March 8, 2026, 5:16 p.m. |
Created at: March 8, 2026, 3:16 p.m.