Triple
T16501316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sun Bowl |
E400805
|
entity |
| Predicate | televisionCoverageStart |
P118394
|
FINISHED |
| Object | 1968 |
—
|
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: 1968 | Statement: [Sun Bowl, televisionCoverageStart, 1968]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: televisionCoverageStart Context triple: [Sun Bowl, televisionCoverageStart, 1968]
-
A.
televisionSyndicationStart
Indicates the date or point in time when a television program first began being distributed for syndication beyond its original broadcast outlet.
-
B.
formerTelevisionCoverage
Indicates that an entity previously provided television coverage of another entity but no longer does so.
-
C.
partialTelevisionCoverage
Indicates that the subject provides or receives television coverage that is limited in scope, duration, or geographic reach rather than full or comprehensive coverage.
-
D.
tvCoverage
chosen
Indicates that an entity provides or is the subject of television broadcast coverage for another entity or event.
-
E.
televisionRoleStart
Indicates the point in time when an entity begins performing or holding a particular role on a television production.
- 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e4f7b7c8190adb5a113f798484f |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296902d6c8190884ddb612b8c5b36 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.