Triple
T16317885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Top of the Heap |
E396217
|
entity |
| Predicate | hasRuntimePerEpisode |
P11339
|
FINISHED |
| Object | approximately 22 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 22 minutes | Statement: [Top of the Heap, hasRuntimePerEpisode, approximately 22 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRuntimePerEpisode Context triple: [Top of the Heap, hasRuntimePerEpisode, approximately 22 minutes]
-
A.
hasEpisodeRuntime
chosen
Indicates the duration of time that each individual episode of a series or show runs.
-
B.
hasEpisodeCountPerSeries
Indicates a relationship where a series is associated with the number of episodes it contains.
-
C.
hasEpisodeLengthType
Indicates the type or category of duration associated with an episode (e.g., standard length, short, extended).
-
D.
hasEpisodes
Indicates that one entity (typically a series or show) contains or is composed of multiple episode entities.
-
E.
runningTimeMiniSeriesVersion
Indicates the duration of the mini-series version of a work, typically measured in time units such as minutes.
- 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e296b31b988190bb1fde36dae11bbd |
completed | April 17, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69e219fc72c881909d452274e7af8238 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.