Triple

T22504781
Position Surface form Disambiguated ID Type / Status
Subject FR0013326246 E556360 entity
Predicate standard P1587 FINISHED
Object ISO 6166 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 6166 | Statement: [FR0013326246, standard, ISO 6166]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ISO 6166
Context triple: [FR0013326246, 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 3664
    ISO 3664 is an international standard that specifies viewing conditions for the visual assessment of images and printed materials, particularly in the graphic arts and photography industries.
  • C. ISO 9564
    ISO 9564 is an international standard that specifies security requirements and formats for personal identification number (PIN) management in card-based financial transactions.
  • D. 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.
  • E. ISO 6160:1979
    ISO 6160:1979 is an international standard that specifies the syntax and features of the PL/I programming language.
  • 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_69e11e555edc81909ca803587dafd747 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15d5ac5808190a66f9111c350f4dc completed April 29, 2026, 1:22 a.m.
Created at: April 16, 2026, 8:50 p.m.