Triple
T17036303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twelve Minutes |
E413328
|
entity |
| Predicate | loopDuration |
P75971
|
FINISHED |
| Object | 12 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: 12 minutes | Statement: [Twelve Minutes, loopDuration, 12 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loopDuration Context triple: [Twelve Minutes, loopDuration, 12 minutes]
-
A.
frameDuration
Indicates the length of time that a single frame in a sequence (such as video or animation) is displayed before advancing to the next frame.
-
B.
timeIntervalLength
chosen
Indicates the duration or length of a specified time interval.
-
C.
loopType
Indicates the specific kind or category of loop structure or iteration pattern used in a process or control flow.
-
D.
eraDuration
Indicates the length of time that a particular era or period spans.
-
E.
timingParameter
Indicates a relationship where one entity specifies or controls a temporal setting, constraint, or configuration parameter that determines the timing behavior of another entity or process.
- 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_69d886cd18288190b006abab23f811b7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d8f26f50819085dfd0fbecd6394d |
completed | April 18, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69e35d5be7f48190af9db67a1e23850f |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:33 a.m.