Triple
T20615067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 18774 |
E506544
|
entity |
| Predicate | technicalCommittee |
P1380
|
FINISHED |
| Object | ISO/TC 68 Financial services |
—
|
NE NERFINISHED |
How this triple was built (3 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 Financial services | Statement: [ISO 18774, technicalCommittee, ISO/TC 68 Financial services]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ISO/TC 68 Financial services Context triple: [ISO 18774, technicalCommittee, ISO/TC 68 Financial services]
-
A.
IEEE Finance Committee
The IEEE Finance Committee is a governing body within the Institute of Electrical and Electronics Engineers responsible for overseeing the organization’s financial policies, planning, and fiscal management.
-
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.
FSB Standing Committee on Standards Implementation
The FSB Standing Committee on Standards Implementation is a key body within the Financial Stability Board responsible for monitoring, assessing, and promoting the implementation of international financial regulatory standards across jurisdictions.
-
D.
ISO/TC 68/SC 8
ISO/TC 68/SC 8 is a subcommittee of ISO Technical Committee 68 responsible for developing international standards related to reference data for the financial services industry.
-
E.
ISO/TC 68/SC 4
ISO/TC 68/SC 4 is a subcommittee of ISO Technical Committee 68 responsible for developing international standards related to financial services information and communication.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: ISO/TC 68 Financial services Target entity description: ISO/TC 68 Financial services is an ISO technical committee responsible for developing international standards for banking, securities, and other financial services to support interoperability, security, and efficiency in global finance.
-
A.
IEEE Finance Committee
The IEEE Finance Committee is a governing body within the Institute of Electrical and Electronics Engineers responsible for overseeing the organization’s financial policies, planning, and fiscal management.
-
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.
FSB Standing Committee on Standards Implementation
The FSB Standing Committee on Standards Implementation is a key body within the Financial Stability Board responsible for monitoring, assessing, and promoting the implementation of international financial regulatory standards across jurisdictions.
-
D.
ISO/TC 68/SC 8
ISO/TC 68/SC 8 is a subcommittee of ISO Technical Committee 68 responsible for developing international standards related to reference data for the financial services industry.
-
E.
ISO/TC 68/SC 4
ISO/TC 68/SC 4 is a subcommittee of ISO Technical Committee 68 responsible for developing international standards related to financial services information and communication.
- F. None of above. chosen
Provenance (2 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_69e0b4bc90988190ac360aaf645efc1d |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aadaf47881909e93efb535c6c1e3 |
completed | April 20, 2026, 10:38 p.m. |
Created at: April 16, 2026, 11:41 a.m.