Triple

T26253886
Position Surface form Disambiguated ID Type / Status
Subject extended binary Golay code E656668 entity
Predicate shortenedVersion P136939 FINISHED
Object binary Golay code [23,12,7] LITERAL 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: binary Golay code [23,12,7] | Statement: [extended binary Golay code, shortenedVersion, binary Golay code [23,12,7]]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: shortenedVersion
Context triple: [extended binary Golay code, shortenedVersion, binary Golay code [23,12,7]]
  • A. wasShortened
    Indicates that something has been made shorter in length, duration, or extent compared to its original form.
  • B. reducedVersionOf chosen
    Indicates that one entity is a simplified, shortened, or otherwise less extensive form of another entity while preserving its essential content or function.
  • C. shortenedInService
    Indicates that an entity’s length, duration, or extent has been reduced as a result of its use or operation in service.
  • D. shortFormat
    Indicates that something is presented in a condensed or abbreviated form compared to its full or standard representation.
  • E. expandedVersionTitle
    Indicates that one title is the name used for an expanded or extended version of another work.
  • F. None of above.

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_69ee5b4d25ac819086acb51184602576 completed April 26, 2026, 6:37 p.m.
NER Named-entity recognition batch_69f60dcc29cc81908880bd825cb12141 completed May 2, 2026, 2:44 p.m.
PD Predicate disambiguation batch_69f5f7fd90fc81909055b211368f9139 completed May 2, 2026, 1:11 p.m.
Created at: April 26, 2026, 9:08 p.m.