Triple

T26253874
Position Surface form Disambiguated ID Type / Status
Subject extended binary Golay code E656668 entity
Predicate numberOfCodewords P194799 FINISHED
Object 4096 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: 4096 | Statement: [extended binary Golay code, numberOfCodewords, 4096]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: numberOfCodewords
Context triple: [extended binary Golay code, numberOfCodewords, 4096]
  • A. hasCodewordsOfWeight
    Indicates that one entity (typically a code) possesses codewords whose Hamming weight equals the specified value in the related entity.
  • B. parityOfCodewords
    Indicates that the relationship concerns whether the number of codewords (or bits within them) is even or odd, i.e., their parity.
  • C. codeword
    Indicates that one entity serves as a codeword or encoded representation used to convey, reference, or stand in for another entity within a coding or communication system.
  • D. codeLengthSymbol
    Indicates a relationship where a symbol is associated with, or assigned, a specific code length (such as in an encoding or compression scheme).
  • E. numericCompanionCode
    Indicates that one entity is associated with another through a specific numeric companion code used to link or reference them.
  • F. None of above. chosen

Provenance (4 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_69fd884cb2b48190b6acd473430d9e19 completed May 8, 2026, 6:53 a.m.
PD Predicate disambiguation batch_69fd8709ca208190a8bab836f0156af5 completed May 8, 2026, 6:47 a.m.
PDg Predicate description generation batch_69fd884b9d908190833de9500ff6d62a completed May 8, 2026, 6:52 a.m.
Created at: April 26, 2026, 9:08 p.m.