Triple
T7199116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bell & Howell Zoomatic Director Series Model 414 PD |
E168691
|
entity |
| Predicate | typicalFrameRate |
P17346
|
FINISHED |
| Object | 18 frames per second |
—
|
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: 18 frames per second | Statement: [Bell & Howell Zoomatic Director Series Model 414 PD, typicalFrameRate, 18 frames per second]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFrameRate Context triple: [Bell & Howell Zoomatic Director Series Model 414 PD, typicalFrameRate, 18 frames per second]
-
A.
propertyType_maxFramerate
Indicates the maximum frame rate value that the property can support or is configured to allow.
-
B.
originalFrameRate
chosen
Indicates the frame rate at which the original media content was captured or encoded before any conversion or processing.
-
C.
typicalResolution
Indicates the usual or standard level of detail or clarity at which something (such as an image, display, or representation) is normally rendered or presented.
-
D.
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.
-
E.
supportsVariableRefreshRate
Indicates that one entity provides compatibility with or functionality for dynamically adjusting refresh rates in coordination with another entity.
- 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_69c68a5376748190bb500f03df86e93e |
completed | March 27, 2026, 1:46 p.m. |
| NER | Named-entity recognition | batch_69c6e92b8bc08190bfcdd34ce42e3448 |
completed | March 27, 2026, 8:31 p.m. |
| PD | Predicate disambiguation | batch_69c6e757fed4819091b0a096e3befc3a |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:52 p.m.