Triple
T5558110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kid Auto Races at Venice |
E145697
|
entity |
| Predicate | runningTimeCategory |
P47557
|
FINISHED |
| Object | short film |
—
|
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: short film | Statement: [Kid Auto Races at Venice, runningTimeCategory, short film]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runningTimeCategory Context triple: [Kid Auto Races at Venice, runningTimeCategory, short film]
-
A.
runtimeMinutes
Indicates the total duration of something, typically a media work or process, measured in minutes.
-
B.
durationCategory
chosen
Indicates the classification of an event or state based on how long it lasts, grouping it into a specific duration range or type.
-
C.
typicalRuntimeRange
Indicates the usual lower and upper bounds of time typically required for an entity to run or complete its operation.
-
D.
runsFrom
Indicates that one entity flees or escapes away from another entity.
-
E.
runsApproximately
Indicates that an entity performs a running action in a manner that is close to, but not exactly matching, a specified time, distance, speed, or other running-related measure.
- 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_69c008fcaf788190bafa02a1917ee73b |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0201529a88190bf0135e032b048ea |
completed | March 22, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69c01b10bbf8819098655839c03b7832 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:36 p.m.