Triple
T18770828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO/TC 258 |
E459012
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | ISO/TC 258 |
—
|
NE NERFINISHED |
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/TC 258 | Statement: [ISO/TC 258, abbreviation, ISO/TC 258]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ISO/TC 258 Context triple: [ISO/TC 258, abbreviation, ISO/TC 258]
-
A.
ISO/TC 258
chosen
ISO/TC 258 is an ISO technical committee responsible for developing international standards in the field of project, programme and portfolio management.
-
B.
ISO/TC 207
ISO/TC 207 is the ISO technical committee responsible for developing international standards on environmental management, including the ISO 14000 family.
-
C.
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.
-
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/IEC JTC 1/SC 38
ISO/IEC JTC 1/SC 38 is the international standardization subcommittee responsible for developing and maintaining standards related to cloud computing and distributed platforms.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e59335a01881908731371be1e27a6b |
completed | April 20, 2026, 2:45 a.m. |
Created at: April 10, 2026, 11:52 a.m.