Triple
T26701528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thaddeus Bradley |
E673168
|
entity |
| Predicate | runsShow |
P161137
|
FINISHED |
| Object | magic-debunking television program |
—
|
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: magic-debunking television program | Statement: [Thaddeus Bradley, runsShow, magic-debunking television program]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runsShow Context triple: [Thaddeus Bradley, runsShow, magic-debunking television program]
-
A.
runsFrom
Indicates that one entity flees or escapes away from another entity.
-
B.
startedShowOn
Indicates that an entity initiated or began broadcasting or presenting a particular show on a specified platform, channel, or service.
-
C.
showsThat
Indicates that one entity demonstrates, proves, or provides evidence for the truth or validity of another.
-
D.
runs
Indicates that an entity moves swiftly on foot, typically using its legs in a continuous, rapid motion.
-
E.
runsVia
Indicates that a process, operation, or connection is executed, routed, or carried out through a specified intermediate channel, path, or mechanism.
- 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_69eecda2b49c8190a6c481cfc4c07954 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f61780706c8190bb9eb3d467d9f852 |
completed | May 2, 2026, 3:25 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f6106d346c8190868489f36c65b6ec |
completed | May 2, 2026, 2:55 p.m. |
Created at: April 27, 2026, 3:31 a.m.