Triple
T957799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO/IEC/IEEE 29148 |
E20661
|
entity |
| Predicate | replaces |
P101
|
FINISHED |
| Object | IEEE 830 |
E3022
|
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 830 | Statement: [ISO/IEC/IEEE 29148, replaces, IEEE 830]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IEEE 830 Context triple: [ISO/IEC/IEEE 29148, replaces, IEEE 830]
-
A.
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.
-
B.
IEEE 830 (Software Requirements Specification standard)
chosen
IEEE 830 (Software Requirements Specification standard) is a widely recognized IEEE guideline that defines the recommended structure and content for documenting software requirements in a clear, complete, and verifiable manner.
-
C.
ISO/IEC 8652
ISO/IEC 8652 is the international standard that formally defines the Ada programming language, including its syntax, semantics, and core features.
-
D.
ISO/IEC 23270
ISO/IEC 23270 is the international standard that formally defines the C# programming language specification.
-
E.
ISO/IEC/IEEE 29148
ISO/IEC/IEEE 29148 is an international standard that defines best practices and processes for engineering and managing system and software requirements.
- 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_69a493b21f2881908132dcf45dcd2f36 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3fac2bc8190a66feb70c68899b2 |
completed | March 1, 2026, 9:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a933b259d08190b03989e2b1575085 |
completed | March 5, 2026, 7:41 a.m. |
Created at: March 1, 2026, 7:40 p.m.