Triple
T30644171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canon EOS M6 Mark II |
E780072
|
entity |
| Predicate | hdmiOutput |
P85051
|
FINISHED |
| Object | micro HDMI (Type D) |
—
|
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: micro HDMI (Type D) | Statement: [Canon EOS M6 Mark II, hdmiOutput, micro HDMI (Type D)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hdmiOutput Context triple: [Canon EOS M6 Mark II, hdmiOutput, micro HDMI (Type D)]
-
A.
hasHDMIPort
chosen
Indicates that one entity (typically a device) is equipped with an HDMI port that can be used to connect to another entity.
-
B.
hasCompositeVideoOutput
Indicates that a device provides a composite video output connection for transmitting standard-definition analog video signals.
-
C.
hdmiVersion
Indicates the specific HDMI standard or version associated with a device, port, or connection.
-
D.
videoOutputConnector
Indicates a relationship where a device or component provides a connector used to output video signals to an external display or receiver.
-
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_69f224a50ebc81909b961a94c7f66b12 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a58cd808190bc1cdaa106291084 |
completed | May 2, 2026, 11:35 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:29 p.m.