Triple
T26253884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | extended binary Golay code |
E656668
|
entity |
| Predicate | dualCode |
P160417
|
FINISHED |
| Object | extended binary Golay code |
—
|
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: extended binary Golay code | Statement: [extended binary Golay code, dualCode, extended binary Golay code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dualCode Context triple: [extended binary Golay code, dualCode, extended binary Golay code]
-
A.
designCode
Indicates that one entity creates, specifies, or defines the design or coding scheme used by another entity.
-
B.
numericCompanionCode
Indicates that one entity is associated with another through a specific numeric companion code used to link or reference them.
-
C.
secondaryCode
Indicates that an entity is associated with an additional, subordinate, or alternative code that complements a primary code.
-
D.
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.
-
E.
fourCornerCode
Indicates a standardized four-character code used to classify or identify something based on its four key components or positions.
- 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_69f60dcc29cc81908880bd825cb12141 |
completed | May 2, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f600be0de88190989611e952b03117 |
completed | May 2, 2026, 1:48 p.m. |
Created at: April 26, 2026, 9:08 p.m.