Triple
T26253871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | extended binary Golay code |
E656668
|
entity |
| Predicate | correctsUpTo |
P161690
|
FINISHED |
| Object | 3 errors per codeword |
—
|
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: 3 errors per codeword | Statement: [extended binary Golay code, correctsUpTo, 3 errors per codeword]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: correctsUpTo Context triple: [extended binary Golay code, correctsUpTo, 3 errors per codeword]
-
A.
Höhepunkt
Indicates the climax or peak point reached within an event, process, or development.
-
B.
endsUp
Indicates that one entity ultimately arrives at, becomes, or results in another state, condition, or location after some process or sequence of events.
-
C.
ascendedTo
Indicates that one entity rose, climbed, or moved upward to reach the position, level, or location of another entity.
-
D.
advancedThrough
Indicates that an entity has progressed or moved forward within, or as a result of, a particular medium, stage, process, or pathway.
-
E.
الجمهور الأساسي
Indicates the primary or main audience that something is intended to reach or address.
- 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_69f6200ac60481909895c61d050b1338 |
completed | May 2, 2026, 4:02 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61f109ef48190873bfe18638d2046 |
completed | May 2, 2026, 3:58 p.m. |
Created at: April 26, 2026, 9:08 p.m.