Triple
T13232763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US1667641005 |
E315063
|
entity |
| Predicate | standard |
P1587
|
FINISHED |
| Object | ISO 6166 |
E118835
|
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 6166 | Statement: [US1667641005, standard, ISO 6166]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ISO 6166 Context triple: [US1667641005, standard, ISO 6166]
-
A.
ISO 6166
chosen
ISO 6166 is an international standard that defines the structure and assignment of International Securities Identification Numbers (ISINs) used to uniquely identify financial securities worldwide.
-
B.
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.
-
C.
ISO 6160:1979
ISO 6160:1979 is an international standard that specifies the syntax and features of the PL/I programming language.
-
D.
ISO 843
ISO 843 is the international standard that defines how to systematically transliterate Modern Greek characters into Latin script.
-
E.
ISO 7098
ISO 7098 is an international standard that specifies the rules for the romanization of Chinese characters using the Hanyu Pinyin system.
- 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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d34ff288190bdb550a019b7a470 |
completed | April 10, 2026, 11:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6ff2dca2c81909cab1aa868ad575d |
completed | May 3, 2026, 7:54 a.m. |
Created at: April 9, 2026, 9:22 p.m.