Triple
T13275839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 259 |
E316186
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | ISO 259-2 |
E316186
|
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 259-2 | Statement: [ISO 259, hasPart, ISO 259-2]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ISO 259-2 Context triple: [ISO 259, hasPart, ISO 259-2]
-
A.
ISO 259
chosen
ISO 259 is an international standard that defines a systematic method for the transliteration of Hebrew characters into the Latin alphabet.
-
B.
ISO 10589
ISO 10589 is the international standard that defines the Intermediate System to Intermediate System (IS-IS) routing protocol used for exchanging routing information within an autonomous system.
-
C.
ISO 7775
ISO 7775 is an older international standard that defined message formats for securities transactions and related financial communications, later superseded by ISO 15022.
-
D.
ISO 3297
ISO 3297 is the international standard that defines the structure, assignment, and use of the International Standard Serial Number (ISSN) for identifying serial publications.
-
E.
ISO 23950
ISO 23950 is an international standard that defines the Z39.50 client-server protocol for searching and retrieving information from remote databases in a networked environment.
- 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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99042f56c819082440c89c0adc442 |
completed | April 11, 2026, 12:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f716cfea308190836eb4892e7c5eb4 |
completed | May 3, 2026, 9:35 a.m. |
Created at: April 9, 2026, 9:26 p.m.