Triple
T5398648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BBC HD |
E120718
|
entity |
| Predicate | fullServiceStartDate |
P288
|
FINISHED |
| Object | 2007-12-01 |
—
|
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-12-01 | Statement: [BBC HD, fullServiceStartDate, 2007-12-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullServiceStartDate Context triple: [BBC HD, fullServiceStartDate, 2007-12-01]
-
A.
serviceEntryDate
Indicates the date on which a service or duty officially began or was first entered into the record.
-
B.
startDate
chosen
Indicates the point in time when an event, state, or relationship begins.
-
C.
fullOperationDate
Indicates the date on which an operation or process is fully carried out or becomes completely effective.
-
D.
fullLineOpeningDate
Indicates the date on which an entire line (such as a route, service, or system) was officially opened for operation.
-
E.
endDateOfficialUse
Indicates the date on which the official use or validity of something (such as a document, status, or authorization) comes to an end.
- 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_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. |
Created at: March 20, 2026, 2:04 p.m.