Triple
T30358469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L-Mount Alliance systems |
E772208
|
entity |
| Predicate | usesMountType |
P2519
|
FINISHED |
| Object | Leica L-mount |
—
|
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 L-mount | Statement: [L-Mount Alliance systems, usesMountType, Leica L-mount]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMountType Context triple: [L-Mount Alliance systems, usesMountType, Leica L-mount]
-
A.
mountType
chosen
Indicates the manner or configuration in which one object is mounted or attached to another.
-
B.
hasMountingFeature
Indicates that one entity includes or provides a structural feature intended for mounting or attaching another entity.
-
C.
hasMount
Indicates that an entity is equipped with, riding, or otherwise using another entity as a mount for transportation or support.
-
D.
mountingInterface
Indicates that one entity serves as the surface, structure, or connection point onto which another entity is mounted or attached.
-
E.
trainMounting
Indicates a relationship where an entity is boarding or getting onto a train.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: April 29, 2026, 7:57 p.m.