Triple
T30842911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leica M lenses |
E785558
|
entity |
| Predicate | mountIntroducedWith |
P172190
|
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 lenses, mountIntroducedWith, Leica M3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mountIntroducedWith Context triple: [Leica M lenses, mountIntroducedWith, Leica M3]
-
A.
introducedFrom
Indicates that one entity was brought, originated, or caused to appear in a context, system, or environment by another entity.
-
B.
areIntroducedBy
Indicates that one entity becomes known or presented to another entity through the action or mediation of a third party or process.
-
C.
introducedInSystem
Indicates that an entity was first added, implemented, or made available within a particular system.
-
D.
introducedVia
Indicates that one entity was brought to the attention, presence, or awareness of another entity through a specific intermediary, method, or channel.
-
E.
messageIntroducedWith
Indicates that one message is presented or initiated by means of another message or introductory content.
- 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_69f6a9603b208190b3533ea2b441514c |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a915ead881909463ae46419c343e |
completed | May 3, 2026, 1:47 a.m. |
Created at: April 29, 2026, 8:45 p.m.