Triple
T19258758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEC 60529 |
E481589
|
entity |
| Predicate | definesTestMethodsFor |
P16244
|
FINISHED |
| Object | protection against solid foreign objects |
—
|
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: protection against solid foreign objects | Statement: [IEC 60529, definesTestMethodsFor, protection against solid foreign objects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesTestMethodsFor Context triple: [IEC 60529, definesTestMethodsFor, protection against solid foreign objects]
-
A.
testingMethod
Indicates the procedure, technique, or approach used to perform a particular test or evaluation.
-
B.
providesMethodsFor
chosen
Indicates that one entity supplies or defines methods or functionalities that can be used or invoked by another entity.
-
C.
testsIn
Indicates that one entity conducts or performs tests within, on, or using another entity.
-
D.
testedFor
Indicates that an entity has been examined or analyzed to determine the presence, absence, or level of another specified entity or condition.
-
E.
commonTest
Indicates that two or more entities share the same test, testing procedure, or evaluation in common.
- 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_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb8752488190ae2dfd2d79373a4b |
completed | April 20, 2026, 10:10 a.m. |
| PD | Predicate disambiguation | batch_69e4dd002d00819088b625056edfb74e |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:28 p.m.