Triple
T30532272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canon EOS R6 |
E777036
|
entity |
| Predicate | batteryCompatibility |
P34359
|
FINISHED |
| Object | LP-E6N |
—
|
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: LP-E6N | Statement: [Canon EOS R6, batteryCompatibility, LP-E6N]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: batteryCompatibility Context triple: [Canon EOS R6, batteryCompatibility, LP-E6N]
-
A.
busCompatibility
Indicates that two hardware or software components can operate together correctly over the same communication bus or interface.
-
B.
compatibilityModel
Indicates that one entity is defined or evaluated according to a specific compatibility framework, standard, or model in relation to another entity.
-
C.
hasHardwareCompatibilityWith
chosen
Indicates that two hardware components or systems can operate together correctly and reliably without conflicts or incompatibilities.
-
D.
cardCompatibility
Indicates how well two or more cards work together in terms of synergy, effectiveness, or intended combined use.
-
E.
compatibilityCondition
Indicates that a specific requirement or set of criteria must be satisfied for two or more entities to be considered compatible or able to function together.
- 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_69f2249c11508190ae7e955755ccfb01 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6a0ea04888190ac3a813b603bcb5c |
completed | May 3, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 8:18 p.m.