Triple
T30382460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canon RF lens mount |
E772866
|
entity |
| Predicate | compatibleViaAdapterWith |
P181337
|
FINISHED |
| Object | Canon EF lenses |
—
|
NE NERFINISHED |
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: Canon EF lenses | Statement: [Canon RF lens mount, compatibleViaAdapterWith, Canon EF lenses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compatibleViaAdapterWith Context triple: [Canon RF lens mount, compatibleViaAdapterWith, Canon EF lenses]
-
A.
compatibleSign
Indicates that two entities are considered astrologically harmonious or well-matched based on their zodiac signs.
-
B.
hasHardwareCompatibilityWith
Indicates that two hardware components or systems can operate together correctly and reliably without conflicts or incompatibilities.
-
C.
isGenerallyCompatibleWith
Indicates that two entities can typically function or coexist together without significant conflict, issues, or need for special adaptation.
-
D.
compatibleStand
Indicates that one entity can be properly supported or held by another entity’s stand or mounting system.
-
E.
compatibleBrand
Indicates that one brand is suitable for use with, or functions properly alongside, another brand.
- 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_69f2248e3444819081b05712dc6873de |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
| PDg | Predicate description generation | batch_69f7688cea58819098bdfd7c80df7634 |
completed | May 3, 2026, 3:23 p.m. |
Created at: April 29, 2026, 8:01 p.m.