Triple
T30358503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L-Mount Alliance systems |
E772208
|
entity |
| Predicate | hasMountDiameter |
P85624
|
FINISHED |
| Object | approximately 51.6 mm |
—
|
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: approximately 51.6 mm | Statement: [L-Mount Alliance systems, hasMountDiameter, approximately 51.6 mm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMountDiameter Context triple: [L-Mount Alliance systems, hasMountDiameter, approximately 51.6 mm]
-
A.
mountDiameter
chosen
Indicates the size of the circular interface where one component is mounted onto another, typically measured as the diameter of the mounting point or opening.
-
B.
shellDiameter
Indicates the diameter measurement of a shell, typically specifying the distance across it at its widest point.
-
C.
hasRimDiameter
Indicates that one entity has a rim whose diameter is measured by or corresponds to the value or object represented by the other entity.
-
D.
shaftDiameter
Indicates the diameter measurement of a shaft in a mechanical or structural context.
-
E.
bodyDiameter
Indicates the measurement of how wide an object's body is across its broadest cross-section.
- 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_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: April 29, 2026, 7:57 p.m.