Triple
T13218541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 20022 Registration Management Group |
E314685
|
entity |
| Predicate | parentSubcommittee |
P70501
|
FINISHED |
| Object |
ISO TC 68 Subcommittee 9
ISO TC 68 Subcommittee 9 is a technical subcommittee within ISO responsible for standards related to financial services, particularly in the area of securities and related messaging.
|
E1025924
|
NE FINISHED |
How this triple was built (5 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 TC 68 Subcommittee 9 | Statement: [ISO 20022 Registration Management Group, parentSubcommittee, ISO TC 68 Subcommittee 9]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ISO TC 68 Subcommittee 9 Context triple: [ISO 20022 Registration Management Group, parentSubcommittee, ISO TC 68 Subcommittee 9]
-
A.
ISO TC 46/SC 9
ISO TC 46/SC 9 is a subcommittee of the International Organization for Standardization responsible for developing standards related to the identification and description of information and documentation, including identifiers like the International Standard Name Identifier (ISNI).
-
B.
ISO/TC 68/SC 2
ISO/TC 68/SC 2 is a subcommittee of ISO Technical Committee 68 responsible for developing international standards related to financial services, particularly in the area of security.
-
C.
ISO Technical Committee 46
ISO Technical Committee 46 is an international standards body within ISO responsible for developing standards related to information and documentation, including libraries, archives, records management, and publishing.
-
D.
ISO Technical Committee 215
ISO Technical Committee 215 is an international standards body focused on developing and harmonizing health informatics standards for electronic health information and related systems.
-
E.
ISO/TC 258
ISO/TC 258 is an ISO technical committee responsible for developing international standards in the field of project, programme and portfolio management.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: ISO TC 68 Subcommittee 9 Triple: [ISO 20022 Registration Management Group, parentSubcommittee, ISO TC 68 Subcommittee 9]
Generated description
ISO TC 68 Subcommittee 9 is a technical subcommittee within ISO responsible for standards related to financial services, particularly in the area of securities and related messaging.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: ISO TC 68 Subcommittee 9 Target entity description: ISO TC 68 Subcommittee 9 is a technical subcommittee within ISO responsible for standards related to financial services, particularly in the area of securities and related messaging.
-
A.
ISO TC 46/SC 9
ISO TC 46/SC 9 is a subcommittee of the International Organization for Standardization responsible for developing standards related to the identification and description of information and documentation, including identifiers like the International Standard Name Identifier (ISNI).
-
B.
ISO/TC 68/SC 2
chosen
ISO/TC 68/SC 2 is a subcommittee of ISO Technical Committee 68 responsible for developing international standards related to financial services, particularly in the area of security.
-
C.
ISO Technical Committee 46
ISO Technical Committee 46 is an international standards body within ISO responsible for developing standards related to information and documentation, including libraries, archives, records management, and publishing.
-
D.
ISO Technical Committee 215
ISO Technical Committee 215 is an international standards body focused on developing and harmonizing health informatics standards for electronic health information and related systems.
-
E.
ISO/TC 258
ISO/TC 258 is an ISO technical committee responsible for developing international standards in the field of project, programme and portfolio management.
- F. None of above.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentSubcommittee Context triple: [ISO 20022 Registration Management Group, parentSubcommittee, ISO TC 68 Subcommittee 9]
-
A.
parentCommittee
Indicates that one committee serves as the higher-level or overseeing committee for another committee.
-
B.
hadSubcommittee
chosen
Indicates that an entity (typically an organization or committee) possessed or was associated with a subordinate committee or subcommittee.
-
C.
hasNumberOfSubcommittees
Indicates the relationship that specifies how many subcommittees are associated with a given entity.
-
D.
hasSiblingCommittee
Indicates that one committee is recognized as a sibling committee of another, typically meaning they are parallel or equivalent bodies within the same organizational structure.
-
E.
hasCommittee
Indicates that an entity is associated with or overseen by a specific committee.
- F. None of above.
Provenance (6 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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf392e08190949ee4d194566395 |
completed | April 10, 2026, 11:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6ff2085f88190be8cfc309d21f9cb |
completed | May 3, 2026, 7:54 a.m. |
| NEDg | Description generation | batch_69f7036009808190aea595cd542e0cf1 |
completed | May 3, 2026, 8:12 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69f7040e32a4819083a9f4efe96fd9ca |
completed | May 3, 2026, 8:15 a.m. |
| PD | Predicate disambiguation | batch_69d98bc938f081909f123bdf1263ff7f |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:18 p.m.