Triple
T19258730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEC 60529 |
E481589
|
entity |
| Predicate | secondCharacteristicNumeralRange |
P132062
|
FINISHED |
| Object | 0–9 |
—
|
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: 0–9 | Statement: [IEC 60529, secondCharacteristicNumeralRange, 0–9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondCharacteristicNumeralRange Context triple: [IEC 60529, secondCharacteristicNumeralRange, 0–9]
-
A.
secondDigitRepresents
chosen
Indicates that the second digit in a numeric or coded value encodes or signifies a specific attribute, category, or meaning within that value.
-
B.
secondLetter
Indicates that one entity is the second letter (in sequence or position) of another entity, typically a string or word.
-
C.
secondLetterRepresents
Indicates that the second letter of one entity stands for, symbolizes, or denotes another entity or concept.
-
D.
secondPartRepresents
Indicates that one part of something serves as the representation, expression, or depiction of a preceding part.
-
E.
secondSeries
Indicates that one entity is the second installment or season in a series relative 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_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.