Triple
T18194891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 20121 |
E435633
|
entity |
| Predicate | developedBy |
P73
|
FINISHED |
| Object | ISO Technical Committee ISO/TC 250 |
—
|
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 Technical Committee ISO/TC 250 | Statement: [ISO 20121, developedBy, ISO Technical Committee ISO/TC 250]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ISO Technical Committee ISO/TC 250 Context triple: [ISO 20121, developedBy, ISO Technical Committee ISO/TC 250]
-
A.
ISO Technical Committee ISO/TC 176
ISO Technical Committee ISO/TC 176 is the ISO body responsible for developing and maintaining international standards on quality management and quality assurance, including the ISO 9000 series.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
ISO TC 68
ISO TC 68 is the ISO technical committee responsible for developing international standards for financial services, including banking, securities, and related financial messaging.
- 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 Technical Committee ISO/TC 250 Target entity description: ISO Technical Committee ISO/TC 250 is a specialized ISO body responsible for developing international standards related to sustainable event management, including ISO 20121.
-
A.
ISO Technical Committee ISO/TC 176
ISO Technical Committee ISO/TC 176 is the ISO body responsible for developing and maintaining international standards on quality management and quality assurance, including the ISO 9000 series.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
ISO TC 68
ISO TC 68 is the ISO technical committee responsible for developing international standards for financial services, including banking, securities, and related financial messaging.
- 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_69d8b90c7ec081909b4694ccecb449c6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e0d1eb1c81908c20b6d15e9c4e8e |
completed | April 19, 2026, 2:04 p.m. |
Created at: April 10, 2026, 10:31 a.m.