Triple
T868166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 27001 |
E18752
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ISO/IEC standard |
C5534
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: ISO/IEC standard Context triple: [ISO 27001, instanceOf, ISO/IEC standard]
-
A.
IEEE standard
An IEEE standard is a formally documented set of technical specifications and guidelines developed and maintained by the Institute of Electrical and Electronics Engineers to ensure interoperability, safety, and quality across electrical, electronic, and computing technologies.
-
B.
ISO standard code set
A standardized collection of internationally recognized codes defined by the International Organization for Standardization (ISO) to uniquely and consistently represent specific types of data, such as countries, currencies, languages, or measurements.
-
C.
Internet standardization document
An Internet standardization document is an authoritative specification that defines technical protocols, formats, or practices to ensure interoperability and consistent behavior across the global Internet.
-
D.
IETF standard
An IETF standard is a formal, consensus-based technical specification developed by the Internet Engineering Task Force that defines protocols, formats, and best practices to ensure interoperability and reliable operation of the Internet.
-
E.
standards-setting organization
A standards-setting organization is an entity that develops, maintains, and promotes agreed-upon technical, professional, or procedural norms to ensure compatibility, quality, and interoperability across industries or sectors.
- F. None of above. chosen
Provenance (1 batch)
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_69a4938ce8688190a24bdfef82ba7d21 |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:39 p.m.