Triple
T23443156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Animation Domination |
E565456
|
entity |
| Predicate | typicalRuntimePerNight |
P152308
|
FINISHED |
| Object | 120 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: 120 minutes | Statement: [Animation Domination, typicalRuntimePerNight, 120 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRuntimePerNight Context triple: [Animation Domination, typicalRuntimePerNight, 120 minutes]
-
A.
typicalRuntimePerShort
Indicates the usual or average amount of time it takes to complete a short instance of the referenced activity or process.
-
B.
associatedNightTiming
Indicates a relationship where an event, action, or condition is linked specifically to a time period occurring during the night.
-
C.
typicalRuntimeRange
Indicates the usual lower and upper bounds of time typically required for an entity to run or complete its operation.
-
D.
typicalDurationDays
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
-
E.
spendsNight
Indicates that one entity stays overnight or spends the night at the location or with the other entity.
- 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_69e24584f9488190bb32730bd2ce023e |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a64654e88190b530958b27b32412 |
completed | April 29, 2026, 6:33 a.m. |
| PD | Predicate disambiguation | batch_69f061f92da081908e7f1d0cd1e9b01c |
completed | April 28, 2026, 7:30 a.m. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:51 p.m.