Triple
T26525089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disney direct-to-video films |
E670665
|
entity |
| Predicate | commonRuntime |
P176276
|
FINISHED |
| Object | feature-length |
—
|
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: feature-length | Statement: [Disney direct-to-video films, commonRuntime, feature-length]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonRuntime Context triple: [Disney direct-to-video films, commonRuntime, feature-length]
-
A.
runTimeSupport
Indicates that one entity provides or requires support for another entity during its execution at run time.
-
B.
primaryRuntime
Indicates the main runtime environment or platform under which an entity (such as a program, service, or component) is intended to execute.
-
C.
originalRuntime
Indicates the initial or primary duration associated with something, typically before any edits, changes, or adjustments are made.
-
D.
runtimeCategory
Indicates the classification of how or under what conditions an entity operates or executes during its runtime.
-
E.
commonVendorSupport
Indicates that two entities are both supported by, or compatible with, at least one of the same vendors.
- 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6dfcafd0c81908d86662948c539d6 |
completed | May 3, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_69f6df418f488190a5e7ff41f32dceda |
completed | May 3, 2026, 5:38 a.m. |
Created at: April 27, 2026, 1:31 a.m.