Triple
T1042103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Court TV |
E22490
|
entity |
| Predicate | relaunchYear |
P12484
|
FINISHED |
| Object | 2019 |
—
|
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: 2019 | Statement: [Court TV, relaunchYear, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relaunchYear Context triple: [Court TV, relaunchYear, 2019]
-
A.
finalReleaseYear
Indicates the calendar year in which something (such as a product, work, or version) is officially released for the last time.
-
B.
originallyReleasedOn
Indicates the date or platform on which something (such as a work, product, or media item) was first made publicly available.
-
C.
unveiledInYear
chosen
Indicates the specific calendar year in which something was formally revealed or made publicly known.
-
D.
originalPlannedLaunchYear
Indicates the year that was initially scheduled or intended for an entity’s launch before any delays or changes.
-
E.
discoveryYear
Indicates the calendar year in which something was first discovered or identified.
- 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_69a493d91478819094cc01fb65564bc1 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b845fa8c8190a7b69629883b62e2 |
completed | March 1, 2026, 10:05 p.m. |
| PD | Predicate disambiguation | batch_69a4b72ba60881908b017ef3b2b9645e |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.