Triple

T20776387
Position Surface form Disambiguated ID Type / Status
Subject Sub-Committee on Standards and Conformance E511365 entity
Predicate shortName P43 FINISHED
Object SCSC 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: SCSC | Statement: [Sub-Committee on Standards and Conformance, shortName, SCSC]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SCSC
Context triple: [Sub-Committee on Standards and Conformance, shortName, SCSC]
  • A. SCSC chosen
    SCSC is a key APEC sub-committee that works to align standards and conformance procedures across member economies to facilitate regional trade.
  • B. SC
    SC is the vehicle registration code used on license plates for the German town of Schwabach in Bavaria.
  • C. SC
    SC is the vehicle registration code used on license plates for vehicles registered in Częstochowa, a city in southern Poland.
  • D. SC
    SC is the standard two-letter postal abbreviation for the U.S. state of South Carolina.
  • E. SC
    SC is the official Indian Railways station code for Secunderabad Junction, a major railway hub in Telangana, India.
  • 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_69e0b4cac7a48190a715cb3d545df2b4 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c26bbe108190bb7c3e5b416e44fe completed April 21, 2026, 12:18 a.m.
Created at: April 16, 2026, 12:37 p.m.