Triple
T28900202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DIN 41612 |
E732931
|
entity |
| Predicate | hasKeyingOption |
P64003
|
FINISHED |
| Object | mechanical keying to prevent mismating |
—
|
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: mechanical keying to prevent mismating | Statement: [DIN 41612, hasKeyingOption, mechanical keying to prevent mismating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyingOption Context triple: [DIN 41612, hasKeyingOption, mechanical keying to prevent mismating]
-
A.
usesKeyingOption
chosen
Indicates that one entity employs a specific keying option or method as part of its operation or configuration.
-
B.
hasKeySupporter
Indicates that an entity has a primary or crucial supporter who significantly backs or advocates for it.
-
C.
hasKeySystem
Indicates that an entity possesses, uses, or is associated with a particular key-based system (such as for access control, encryption, or identification).
-
D.
hasKeyPolicy
Indicates that an entity is associated with a specific key management or access control policy governing how its keys may be used or managed.
-
E.
hasKeyAct
Indicates that one entity possesses or is associated with a primary or central action related to another entity.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 28, 2026, 8:02 a.m.