Triple
T38629745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The House of Hate |
E937416
|
entity |
| Predicate | runtimeTotalApprox |
P31999
|
FINISHED |
| Object | over 6 hours |
—
|
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: over 6 hours | Statement: [The House of Hate, runtimeTotalApprox, over 6 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runtimeTotalApprox Context triple: [The House of Hate, runtimeTotalApprox, over 6 hours]
-
A.
runtimeApprox
chosen
Indicates an approximate or estimated duration of time that something (such as a process, program, or event) takes to run or complete.
-
B.
prototypeCountApproximate
Indicates that the number of prototypes involved is an estimated or approximate count rather than an exact value.
-
C.
runsTotal
Indicates the total number of runs accumulated or recorded for an entity over a specified period or context.
-
D.
commonTotalLength
Indicates that the entities share the same overall measured length.
-
E.
durationTotal
Indicates the overall length of time for which an event, process, or state persists, typically aggregating all its constituent durations.
- 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_69f76ed5ca3c81909288f61fbf37b359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.