Triple
T19258729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEC 60529 |
E481589
|
entity |
| Predicate | firstCharacteristicNumeralRange |
P135083
|
FINISHED |
| Object | 0–6 |
—
|
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–6 | Statement: [IEC 60529, firstCharacteristicNumeralRange, 0–6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstCharacteristicNumeralRange Context triple: [IEC 60529, firstCharacteristicNumeralRange, 0–6]
-
A.
firstCharacterType
Indicates that the type or category of the first character in a sequence or string has a specified value.
-
B.
firstDigitEncoding
Indicates that one entity encodes or represents the first digit of another entity (such as a number, code, or identifier).
-
C.
firstChassisNumber
Indicates that the associated value is the earliest or initial chassis identification number assigned to a vehicle or mechanical unit.
-
D.
firstSeriesCode
Indicates that an entity is identified as the initial or primary series within a sequence, referenced by a specific code.
-
E.
serialNumberRange
Indicates that there is a specified range of serial numbers within which the related entities or items fall.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e4ddcf50108190a09d0f1291c17374 |
completed | April 19, 2026, 1:51 p.m. |
Created at: April 10, 2026, 1:28 p.m.