Triple
T12848547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Dan Patrick Show |
E307247
|
entity |
| Predicate | typicalRuntimeCategory |
P72996
|
FINISHED |
| Object | daily talk show |
—
|
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: daily talk show | Statement: [The Dan Patrick Show, typicalRuntimeCategory, daily talk show]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRuntimeCategory Context triple: [The Dan Patrick Show, typicalRuntimeCategory, daily talk show]
-
A.
typicalRuntimeRange
Indicates the usual lower and upper bounds of time typically required for an entity to run or complete its operation.
-
B.
runtimeCategory
chosen
Indicates the classification of how or under what conditions an entity operates or executes during its runtime.
-
C.
typicalRuntimePerShort
Indicates the usual or average amount of time it takes to complete a short instance of the referenced activity or process.
-
D.
typicalCPU
Indicates that an entity uses or is associated with a standard or commonly used CPU for its type or category.
-
E.
primaryRuntime
Indicates the main runtime environment or platform under which an entity (such as a program, service, or component) is intended to execute.
- 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_69d7bdf5e7cc8190be357278bc5ba3bb |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9714208f881908f7f8a921362909a |
completed | April 10, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69d96fa3002881908000357b1f95a3ac |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:36 p.m.