Triple
T1937621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEC 60488 |
E41477
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | IEC 60488-15 |
E41477
|
NE 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: IEC 60488-15 | Statement: [IEC 60488, hasPart, IEC 60488-15]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IEC 60488-15 Context triple: [IEC 60488, hasPart, IEC 60488-15]
-
A.
IEC 60488
chosen
IEC 60488 is an international standard issued by the International Electrotechnical Commission that defines digital interface and command protocols for programmable measuring instruments and related control systems.
-
B.
IEC 62591
IEC 62591 is an international standard that defines the WirelessHART industrial wireless communication protocol for process automation and control applications.
-
C.
ISO 10589
ISO 10589 is the international standard that defines the Intermediate System to Intermediate System (IS-IS) routing protocol used for exchanging routing information within an autonomous system.
-
D.
IEEE Std 610.12-2010
IEEE Std 610.12-2010 is an updated IEEE standard that provides a formal glossary of terms and definitions used in software engineering.
-
E.
IEEE 1532
IEEE 1532 is an extension of the JTAG boundary-scan standard that defines in-system programming and configuration procedures for programmable devices such as FPGAs and CPLDs.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a88649b24c819080047f26b6db2ded |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb2c752fc81909baf38ff1cdeb18c |
completed | March 7, 2026, 5:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae892f5bac8190b1033a1eacfab7ef |
completed | March 9, 2026, 8:47 a.m. |
Created at: March 4, 2026, 7:36 p.m.