Triple
T30842869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leica M-mount |
E785557
|
entity |
| Predicate | notableLensFamily |
P65462
|
FINISHED |
| Object | Leica Summicron-M |
E785558
|
NE 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: Leica Summicron-M | Statement: [Leica M-mount, notableLensFamily, Leica Summicron-M]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableLensFamily Context triple: [Leica M-mount, notableLensFamily, Leica Summicron-M]
-
A.
lensSeries
Indicates that one lens belongs to, or is part of, a particular series or product line of lenses.
-
B.
lensType
Indicates the specific kind or category of lens associated with or used by an entity.
-
C.
notableModelFamily
chosen
Indicates that one entity is a prominent or widely recognized model family associated with, produced by, or otherwise notably linked to another entity.
-
D.
laterLensType
Indicates that one lens type occurs or is used at a later time than another lens type in a temporal sequence.
-
E.
usesLensBrand
Indicates that one entity employs or operates using a lens produced by a specific brand.
- F. None of above.
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_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a28bbf4e3e081908eb74bac55d221ab |
completed | June 10, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:45 p.m.