Triple
T5362822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 31010 |
E103060
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | ISO 31000 |
E18758
|
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 31000 | Statement: [ISO 31010, relatedTo, ISO 31000]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ISO 31000 Context triple: [ISO 31010, relatedTo, ISO 31000]
-
A.
ISO 31000
chosen
ISO 31000 is an international standard that provides principles and guidelines for effective risk management applicable to organizations of all types and sizes.
-
B.
ISO 31010
ISO 31010 is an international standard that provides guidelines and a comprehensive toolkit of techniques for risk assessment within risk management frameworks.
-
C.
ISO 22301
ISO 22301 is an international standard that specifies requirements for establishing, implementing, maintaining, and improving a business continuity management system.
-
D.
ISO/IEC 27005
ISO/IEC 27005 is an international standard that provides guidelines for information security risk management within an organization’s overall information security management system.
-
E.
ISO/IEC 27003
ISO/IEC 27003 is an international standard that provides guidance on implementing and managing an information security management system (ISMS) in accordance with ISO/IEC 27001.
- 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_69bd43daa3e4819090b59d127db70e57 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd865b9b808190a1e8c283ba28d645 |
completed | March 20, 2026, 5:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf21ef7acc8190aa7ff990a04ff09c |
completed | March 21, 2026, 10:55 p.m. |
Created at: March 20, 2026, 2:02 p.m.