Triple
T18248774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drama Short Film Festival |
E437025
|
entity |
| Predicate | typicalDurationOfWorks |
P32671
|
FINISHED |
| Object | up to 30 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: up to 30 minutes | Statement: [Drama Short Film Festival, typicalDurationOfWorks, up to 30 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDurationOfWorks Context triple: [Drama Short Film Festival, typicalDurationOfWorks, up to 30 minutes]
-
A.
typicalDurationDays
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
-
B.
workLength
chosen
Indicates the duration or length of time associated with a particular work or task.
-
C.
hasTypicalPerformanceDuration
Indicates the usual or expected length of time that a performance or activity typically lasts.
-
D.
typicalRecordingDuration
Indicates the usual or standard length of time that something is recorded.
-
E.
intendedDuration
Indicates the planned or expected length of time for which an action, event, or state is meant to occur or remain in effect.
- 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_69d8b91104e08190a8241f7d260a5162 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4fd7fa3708190baefd8d938d20807 |
completed | April 19, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69e44fcdee748190bae6fb76e0cb22f3 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:33 a.m.