Triple
T24633784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ITV North of England |
E609749
|
entity |
| Predicate | providedProgramming |
P156850
|
FINISHED |
| Object | ITV network programming |
—
|
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: ITV network programming | Statement: [ITV North of England, providedProgramming, ITV network programming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providedProgramming Context triple: [ITV North of England, providedProgramming, ITV network programming]
-
A.
primaryProgramming
Indicates that one entity serves as the main or most important programming or coding language, tool, or environment used by another entity.
-
B.
programmingBy
Indicates that one entity is created, implemented, or developed through the act of programming performed by another entity.
-
C.
program
Indicates that an entity creates, writes, or develops a computer program or software application.
-
D.
offersProfessionalPrograms
Indicates that an entity provides formal, career-oriented educational or training programs to others.
-
E.
recommendedProgram
Indicates that one entity suggests or endorses another entity as a suitable or preferred program for a particular purpose or user.
- 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_69e2c4d28f848190ac38c400060e943d |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be064ff88190b5d9e5ec75a41242 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6d0ab708190b2e3b94dd20ca76b |
completed | April 30, 2026, 12:48 a.m. |
| PDg | Predicate description generation | batch_69f2b8b8bc5881908df49c0b07110246 |
completed | April 30, 2026, 2:04 a.m. |
Created at: April 18, 2026, 2:32 a.m.