Triple
T30644172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canon EOS M6 Mark II |
E780072
|
entity |
| Predicate | bodyDesign |
P168483
|
FINISHED |
| Object | compact rangefinder-style body |
—
|
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: compact rangefinder-style body | Statement: [Canon EOS M6 Mark II, bodyDesign, compact rangefinder-style body]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyDesign Context triple: [Canon EOS M6 Mark II, bodyDesign, compact rangefinder-style body]
-
A.
bodyDesignDerivedFrom
Indicates that the design or structural form of one body is derived, adapted, or developed from another body’s design.
-
B.
carbodyMaterial
Indicates the material from which a vehicle’s body or main structural shell is made.
-
C.
bodyTypes
chosen
Indicates a relationship where one or more body types are associated with or assigned to an entity.
-
D.
bodyworkFeature
Indicates a relationship where a vehicle or object possesses a specific characteristic or component of its external body structure.
-
E.
oreBodyStyle
Indicates the specific body style or physical form that an ore or mineral deposit exhibits.
- 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.