Triple
T5398647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BBC HD |
E120718
|
entity |
| Predicate | trialServiceEndDate |
P63743
|
FINISHED |
| Object | 2007-11-30 |
—
|
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: 2007-11-30 | Statement: [BBC HD, trialServiceEndDate, 2007-11-30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trialServiceEndDate Context triple: [BBC HD, trialServiceEndDate, 2007-11-30]
-
A.
deFactoEndDate
Indicates the date on which a relationship, status, or condition effectively ended in practice, regardless of any formal or official end date.
-
B.
typicalEndDate
Indicates the date on which something, such as an event, process, or period, normally or customarily ends.
-
C.
commissioningEndDate
Indicates the date on which the commissioning process or commissioning-related responsibilities are completed or terminated.
-
D.
setsTermEndDateFor
Indicates setting or assigning the end date of a term or period for another entity.
-
E.
trialDate
Indicates the specific calendar date on which a legal trial or court proceeding is scheduled or took place.
- 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_69bd4637b92c8190b815b6443ae4b323 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8932b8bc8190bd31e11b167a7212 |
completed | March 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69bd84660ea08190a641084814fcf94d |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd8931302c81908afcb0f011e91f09 |
completed | March 20, 2026, 5:51 p.m. |
Created at: March 20, 2026, 2:04 p.m.