Triple
T18958813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Dean Martin Celebrity Roast |
E463853
|
entity |
| Predicate | hasTypicalRuntime |
P109104
|
FINISHED |
| Object | approximately 60 minutes |
—
|
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: approximately 60 minutes | Statement: [The Dean Martin Celebrity Roast, hasTypicalRuntime, approximately 60 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalRuntime Context triple: [The Dean Martin Celebrity Roast, hasTypicalRuntime, approximately 60 minutes]
-
A.
typicalRuntimeRange
Indicates the usual lower and upper bounds of time typically required for an entity to run or complete its operation.
-
B.
hasTypicalPerformanceDuration
chosen
Indicates the usual or expected length of time that a performance or activity typically lasts.
-
C.
typicalRuntimePerShort
Indicates the usual or average amount of time it takes to complete a short instance of the referenced activity or process.
-
D.
hasTypicalUseTime
Indicates the usual or expected duration or time period during which something is commonly used or in operation.
-
E.
hasRunningTimeCategory
Indicates that an entity is associated with a specific category based on its running time or duration.
- 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_69d8dcffc278819086792a4ebfddfafa |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d5d057a48190b82b5788b3281e28 |
completed | April 20, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f437648190b85650dae8885d48 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, noon