Triple
T9030010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE 1815 |
E216144
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | IEEE Std 1815 |
E216144
|
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: IEEE Std 1815 | Statement: [IEEE 1815, abbreviation, IEEE Std 1815]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IEEE Std 1815 Context triple: [IEEE 1815, abbreviation, IEEE Std 1815]
-
A.
IEEE 1815
chosen
IEEE 1815 is an IEEE standard that formally defines the DNP3 protocol used for reliable, secure communication in electric power and industrial control systems.
-
B.
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.
-
C.
IEEE 1196
IEEE 1196 is the IEEE standard that formally defines the NuBus computer bus architecture used in various workstation and personal computer systems.
-
D.
ANSI/IEEE 1014
ANSI/IEEE 1014 is the formal standard designation for the VMEbus computer bus architecture widely used in embedded and industrial systems.
-
E.
IEEE 1496-1993
IEEE 1496-1993 is an IEEE standard that specifies the SBus computer bus architecture used primarily in Sun Microsystems workstations and servers.
- 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a9e0aa881908886f453c51ecd0e |
completed | April 1, 2026, 12:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfeb83e8988190bf29baa1aff11ac0 |
completed | April 3, 2026, 4:32 p.m. |
Created at: March 30, 2026, 7:08 p.m.