Triple
T27217631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yorkshire Television |
E681181
|
entity |
| Predicate | notableNewsProgramme |
P48038
|
FINISHED |
| Object | Calendar |
—
|
NE NERFINISHED |
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: Calendar | Statement: [Yorkshire Television, notableNewsProgramme, Calendar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableNewsProgramme Context triple: [Yorkshire Television, notableNewsProgramme, Calendar]
-
A.
notableBroadcast
Indicates that an entity is recognized for having made a significant or widely known broadcast.
-
B.
notableShow
Indicates that a show is especially prominent, distinguished, or significant in some noteworthy way.
-
C.
notableProgramType
Indicates that the subject is recognized for or associated with a particular type or category of program.
-
D.
notableProgrammeStrand
chosen
Indicates that an entity is a significant or distinguished program series or strand associated with another entity (such as an organization, channel, or event).
-
E.
notableBroadcastFeature
Indicates that something has a distinctive or noteworthy characteristic related to its broadcast or transmission.
- 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_69eefac9f64c8190a07490fe0c8b72a3 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69ffa5f31c8881908c26e2aa52df6ece |
completed | May 9, 2026, 9:24 p.m. |
| PD | Predicate disambiguation | batch_69ffa42aee408190ad1a5f285688b338 |
completed | May 9, 2026, 9:16 p.m. |
Created at: April 27, 2026, 9:41 a.m.