Triple
T18022417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark Hunter |
E431157
|
entity |
| Predicate | radioShowFormat |
P9706
|
FINISHED |
| Object | late-night talk |
—
|
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: late-night talk | Statement: [Mark Hunter, radioShowFormat, late-night talk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radioShowFormat Context triple: [Mark Hunter, radioShowFormat, late-night talk]
-
A.
radioFormat
chosen
Indicates the specific type or style of radio programming or broadcast format associated with an entity.
-
B.
typicalBroadcastFormat
Indicates the usual or standard broadcast format in which something (such as a program or content) is typically transmitted.
-
C.
radioFormatSuccess
Indicates that a particular radio format or programming approach has achieved success, such as strong performance or positive outcomes.
-
D.
radioAnnouncers
Indicates that one entity serves as a radio announcer for, or in association with, another entity.
-
E.
hasRadioShow
Indicates that an entity hosts, produces, or is responsible for a radio show.
- 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_69d8b9050fb48190890155145deb0a66 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b9c3a2c48190bbe4a0581466cd2f |
completed | April 19, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_69e3f904b8048190add43883cd7cb191 |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:24 a.m.