Triple
T868689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 21500 |
E18762
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | ISO 21500 |
E18762
|
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 21500 | Statement: [ISO 21500, abbreviation, ISO 21500]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ISO 21500 Context triple: [ISO 21500, abbreviation, ISO 21500]
-
A.
ISO 21500
chosen
ISO 21500 is an international standard that provides high-level guidance and principles for effective project management applicable to organizations of all types and sizes.
-
B.
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.
-
C.
ISO 2108
ISO 2108 is the international standard that defines the structure and use of the International Standard Book Number (ISBN) system for identifying books and related publications.
-
D.
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.
-
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_69a4938ce8688190a24bdfef82ba7d21 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac7f98908190883f71049092c7c8 |
completed | March 1, 2026, 9:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a7a3c9e7ec819081d58634fe0efdcb |
completed | March 4, 2026, 3:15 a.m. |
Created at: March 1, 2026, 7:39 p.m.