Triple
T1009356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO/IEC 12207 |
E21784
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | ISO 12207 |
E21784
|
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: ISO 12207 | Statement: [ISO/IEC 12207, hasAbbreviation, ISO 12207]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ISO 12207 Context triple: [ISO/IEC 12207, hasAbbreviation, ISO 12207]
-
A.
ISO/IEC 12207
chosen
ISO/IEC 12207 is an international standard that defines a comprehensive framework and set of processes for the life cycle management of software systems.
-
B.
IEEE 12207
IEEE 12207 is an international standard that defines processes, activities, and tasks for the life cycle management of software systems.
-
C.
ISO/IEC 15288
ISO/IEC 15288 is an international standard that defines a common framework of processes for the life cycle management of systems, from conception through retirement.
-
D.
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.
-
E.
ISO 7498
ISO 7498 is the international standard that defines the Open Systems Interconnection (OSI) reference model for network communications.
- 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_69a493c53e648190ae8cb76c433fd9a7 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7a3cb608190a2de34a09cd55146 |
completed | March 1, 2026, 10:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac4c0ef95081909ddc4ec480248572 |
completed | March 7, 2026, 4:02 p.m. |
Created at: March 1, 2026, 7:41 p.m.