Triple
T28434389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norman Dale Baker |
E715220
|
entity |
| Predicate | broadcastWork |
P121715
|
FINISHED |
| Object | TNN NASCAR coverage |
—
|
NE NERFINISHED |
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: TNN NASCAR coverage | Statement: [Norman Dale Baker, broadcastWork, TNN NASCAR coverage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broadcastWork Context triple: [Norman Dale Baker, broadcastWork, TNN NASCAR coverage]
-
A.
broadcastingWork
chosen
Indicates that one entity is a broadcasted work (such as a radio or TV program) that is transmitted or made available to an audience by another entity.
-
B.
broadcastFor
Indicates that one entity transmits or disseminates content, information, or a signal on behalf of, or in service of, another entity.
-
C.
broadcastVia
Indicates that an action, message, or content is transmitted or disseminated through a specified medium, channel, or platform.
-
D.
broadcastBlock
Indicates that one entity transmits or disseminates a block (such as a data block or message) to multiple recipients or across a network.
-
E.
broadcastAfter
Indicates that one broadcast event occurs later in time than another broadcast event.
- 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_69efd6b253888190b3c7222ed6a403a8 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 1:41 a.m.