Triple

T22829902
Position Surface form Disambiguated ID Type / Status
Subject ISO/IEC JTC 1/SC 27 E565768 entity
Predicate hasWorkingGroup P1382 FINISHED
Object ISO/IEC JTC 1/SC 27/WG 2 — 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/IEC JTC 1/SC 27/WG 2 | Statement: [ISO/IEC JTC 1/SC 27, hasWorkingGroup, ISO/IEC JTC 1/SC 27/WG 2]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: ISO/IEC JTC 1/SC 27/WG 2
Context triple: [ISO/IEC JTC 1/SC 27, hasWorkingGroup, ISO/IEC JTC 1/SC 27/WG 2]
  • A. ISO/IEC JTC 1/SC 2/WG 5
    ISO/IEC JTC 1/SC 2/WG 5 is a specialized working group within the ISO/IEC committee structure responsible for developing and maintaining international standards related to coded character sets and related encoding technologies.
  • B. ISO/IEC JTC 1/SC 27
    ISO/IEC JTC 1/SC 27 is the international standardization subcommittee responsible for developing standards in information security, cybersecurity, and privacy protection.
  • C. ISO/IEC JTC 1/SC 2/WG 3
    ISO/IEC JTC 1/SC 2/WG 3 is a specialized working group within the ISO/IEC committee structure responsible for developing and maintaining international standards related to coded character sets and related encoding technologies.
  • D. ISO/IEC JTC 1/SC 42
    ISO/IEC JTC 1/SC 42 is the international standards subcommittee responsible for developing and coordinating global standards for artificial intelligence and related data technologies.
  • E. ISO/IEC JTC 1/SC 2
    ISO/IEC JTC 1/SC 2 is the international standardization subcommittee responsible for character sets and coding, including the development and maintenance of the Universal Coded Character Set (UCS).
  • 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/IEC JTC 1/SC 27/WG 2
Target entity description: ISO/IEC JTC 1/SC 27/WG 2 is a specialized working group focused on developing international standards for cryptography and security mechanisms within the broader information security standardization framework.
  • A. ISO/IEC JTC 1/SC 2/WG 5
    ISO/IEC JTC 1/SC 2/WG 5 is a specialized working group within the ISO/IEC committee structure responsible for developing and maintaining international standards related to coded character sets and related encoding technologies.
  • B. ISO/IEC JTC 1/SC 27 chosen
    ISO/IEC JTC 1/SC 27 is the international standardization subcommittee responsible for developing standards in information security, cybersecurity, and privacy protection.
  • C. ISO/IEC JTC 1/SC 2/WG 3
    ISO/IEC JTC 1/SC 2/WG 3 is a specialized working group within the ISO/IEC committee structure responsible for developing and maintaining international standards related to coded character sets and related encoding technologies.
  • D. ISO/IEC JTC 1/SC 42
    ISO/IEC JTC 1/SC 42 is the international standards subcommittee responsible for developing and coordinating global standards for artificial intelligence and related data technologies.
  • E. ISO/IEC JTC 1/SC 2
    ISO/IEC JTC 1/SC 2 is the international standardization subcommittee responsible for character sets and coding, including the development and maintenance of the Universal Coded Character Set (UCS).
  • F. None of above.

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_69e24585ab1c81909b2b5065d15805d5 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17e2ac8d48190b6dc7edc5ad82bc7 completed April 29, 2026, 3:42 a.m.
Created at: April 17, 2026, 3:34 p.m.