Triple
T8305669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WCVB-TV |
E194456
|
entity |
| Predicate | digitalTransitionDate |
P82641
|
FINISHED |
| Object | June 12, 2009 |
—
|
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: June 12, 2009 | Statement: [WCVB-TV, digitalTransitionDate, June 12, 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: digitalTransitionDate Context triple: [WCVB-TV, digitalTransitionDate, June 12, 2009]
-
A.
finalAppTransitionDate
Indicates the date on which the final transition or change of state for the application was completed.
-
B.
dateOfConversion
Indicates the specific date on which an entity changed status, form, or affiliation (e.g., religious, legal, or organizational conversion).
-
C.
automationDate
Indicates the date on which an action, process, or system becomes automated or is scheduled to be handled automatically.
-
D.
integrationDate
Indicates the date on which two or more entities, systems, or components are combined or brought into a unified whole.
-
E.
establishedTransitionPeriod
Indicates that an entity has formally set or defined a specific transition period between two states, conditions, or arrangements.
- 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_69ca82e613e88190bf8139669bbd0d53 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f293db08190912e5e8bb7e940cf |
completed | March 31, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69cb70bb3a708190bc705222092da614 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76d648988190ab0669cc0592e827 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 5:54 p.m.