Triple
T1892030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Handycam |
E41893
|
entity |
| Predicate | supportsVideoFormat |
P24486
|
FINISHED |
| Object | standard definition video |
—
|
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: standard definition video | Statement: [Handycam, supportsVideoFormat, standard definition video]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsVideoFormat Context triple: [Handycam, supportsVideoFormat, standard definition video]
-
A.
usesFootageType
Indicates that one entity employs or incorporates a particular type or category of footage in its content or production.
-
B.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
C.
hasFileFormat
Indicates that one entity (typically a digital file or resource) is encoded, stored, or represented using a specific file format defined by the other entity.
-
D.
supportsType
chosen
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
E.
videoOutput
Indicates that one entity produces or provides video signals or content as output to another entity or medium.
- 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_69a8864b6de0819098d089f6a1b910a7 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb145f96c8190a71bb9e442892e68 |
completed | March 7, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69abafe61bc48190ac9ead027df930e1 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:34 p.m.