Triple
T11651467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Paul Finebaum Show |
E276912
|
entity |
| Predicate | hasHostPersonality |
P100193
|
FINISHED |
| Object | provocative |
—
|
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: provocative | Statement: [The Paul Finebaum Show, hasHostPersonality, provocative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHostPersonality Context triple: [The Paul Finebaum Show, hasHostPersonality, provocative]
-
A.
hostSystem
Indicates that one entity serves as the primary computing or operating environment in which another entity runs, is managed, or is contained.
-
B.
hasMainHost
Indicates that one entity serves as the primary or principal host for another entity.
-
C.
hasBaseSystem
Indicates that one entity is founded upon, derived from, or primarily operates using another entity as its underlying system or framework.
-
D.
supportsGuestArchitecture
Indicates that one entity provides the necessary capabilities or environment to run or host the specified guest architecture of another entity.
-
E.
hostType
Indicates the category or kind of host associated with or responsible for the related entity or activity.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a2cea9308190a13f7dd995ea07a4 |
completed | April 10, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69d85ddc780481909a3bc63832fe2bd2 |
completed | April 10, 2026, 2:18 a.m. |
| PDg | Predicate description generation | batch_69d87f30642c8190ad94fa061cde186b |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 8, 2026, 9:39 p.m.