Triple
T30842840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leica M-mount |
E785557
|
entity |
| Predicate | compatibleWithCamera |
P184006
|
FINISHED |
| Object | Leica M3 |
—
|
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: Leica M3 | Statement: [Leica M-mount, compatibleWithCamera, Leica M3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compatibleWithCamera Context triple: [Leica M-mount, compatibleWithCamera, Leica M3]
-
A.
compatibleCameraType
Indicates that one entity is a type of camera that can properly function or be used in conjunction with another entity.
-
B.
usesCameraType
Indicates that one entity employs or operates a specific type or category of camera.
-
C.
meetsInCamera
Indicates that two or more entities are physically present together in the same camera frame or shot at the same time.
-
D.
hasCamera
Indicates that an entity is equipped with or possesses a camera.
-
E.
supportsCameraControl
Indicates that one entity provides functionality for another entity to remotely manage or adjust camera settings or operations.
- 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_69f224b850848190a4af4ccf8ddadcdf |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7aaabb58c8190bf81673608ecfb6e |
completed | May 3, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f7aa6795f481908940838ee7041ff5 |
completed | May 3, 2026, 8:04 p.m. |
Created at: April 29, 2026, 8:45 p.m.