Triple

T23312955
Position Surface form Disambiguated ID Type / Status
Subject ebXML E590629 entity
Predicate standardizedBy P1371 FINISHED
Object OASIS Technical Committees — 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: OASIS Technical Committees | Statement: [ebXML, standardizedBy, OASIS Technical Committees]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: OASIS Technical Committees
Context triple: [ebXML, standardizedBy, OASIS Technical Committees]
  • A. OASIS Security Services Technical Committee
    The OASIS Security Services Technical Committee is a working group within the OASIS standards organization responsible for developing and maintaining security-related specifications for web services and identity management.
  • B. OASIS DITA Technical Committee
    The OASIS DITA Technical Committee is the standards body within OASIS responsible for developing and maintaining the DITA XML-based architecture for structured, topic-oriented content.
  • C. ISO Technical Committee 68
    ISO Technical Committee 68 is an international standards body responsible for developing and maintaining standards in the field of financial services.
  • D. ISO Technical Committee 215
    ISO Technical Committee 215 is an international standards body focused on developing and harmonizing health informatics standards for electronic health information and related systems.
  • E. Compliance and Interoperability Working Group
    The Compliance and Interoperability Working Group is a technical body within the IBTA focused on ensuring that InfiniBand products from different vendors conform to specifications and operate seamlessly together.
  • 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: OASIS Technical Committees
Target entity description: OASIS Technical Committees are collaborative working groups within the OASIS standards organization that develop open, consensus-based technical specifications for information exchange and interoperability.
  • A. OASIS Security Services Technical Committee
    The OASIS Security Services Technical Committee is a working group within the OASIS standards organization responsible for developing and maintaining security-related specifications for web services and identity management.
  • B. OASIS DITA Technical Committee
    The OASIS DITA Technical Committee is the standards body within OASIS responsible for developing and maintaining the DITA XML-based architecture for structured, topic-oriented content.
  • C. ISO Technical Committee 68
    ISO Technical Committee 68 is an international standards body responsible for developing and maintaining standards in the field of financial services.
  • D. ISO Technical Committee 215
    ISO Technical Committee 215 is an international standards body focused on developing and harmonizing health informatics standards for electronic health information and related systems.
  • E. Compliance and Interoperability Working Group
    The Compliance and Interoperability Working Group is a technical body within the IBTA focused on ensuring that InfiniBand products from different vendors conform to specifications and operate seamlessly together.
  • F. None of above. chosen

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_69e25d1d32188190948eb76909d1dcc3 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1972ca70481909e2415c65964210a completed April 29, 2026, 5:29 a.m.
Created at: April 17, 2026, 5:06 p.m.