Triple
T4616744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO High Level Structure |
E100885
|
entity |
| Predicate | usedInStandard |
P1587
|
FINISHED |
| Object | ISO 22301 |
E458505
|
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 22301 | Statement: [ISO High Level Structure, usedInStandard, ISO 22301]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ISO 22301 Context triple: [ISO High Level Structure, usedInStandard, ISO 22301]
-
A.
ISO 22301
chosen
ISO 22301 is an international standard that specifies requirements for establishing, implementing, maintaining, and improving a business continuity management system.
-
B.
ISO 31000
ISO 31000 is an international standard that provides principles and guidelines for effective risk management applicable to organizations of all types and sizes.
-
C.
ISO 20121
ISO 20121 is an international standard that provides a framework for managing and improving the sustainability of events and event-related activities.
-
D.
ISO 31010
ISO 31010 is an international standard that provides guidelines and a comprehensive toolkit of techniques for risk assessment within risk management frameworks.
-
E.
ISO 26324
ISO 26324 is the international standard that defines the structure, syntax, and functional framework of the Digital Object Identifier (DOI) system for uniquely identifying digital content.
- 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_69bd43cf363c819087fd5ab441b4a3f4 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59e098c08190b769e76937dff700 |
completed | March 20, 2026, 2:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be035a44f08190900bc6898a40e4e9 |
completed | March 21, 2026, 2:32 a.m. |
Created at: March 20, 2026, 1:12 p.m.