Triple
T26253966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | binary Golay code |
E656670
|
entity |
| Predicate | isExtendedTo |
P1673
|
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: [binary Golay code, isExtendedTo, extended binary Golay code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isExtendedTo Context triple: [binary Golay code, isExtendedTo, extended binary Golay code]
-
A.
extendsTo
chosen
Indicates that one entity reaches, stretches, or continues its scope, influence, or coverage up to or into another entity.
-
B.
wasExtendedTo
Indicates that something previously existing was lengthened, expanded, or prolonged to reach a new limit, scope, or duration.
-
C.
extendedFrom
Indicates that one entity is derived by adding to or building upon the scope, content, or structure of another entity.
-
D.
mayExtendTo
Indicates that something has the potential or permission to reach, continue, or be applied up to a specified limit, scope, or boundary.
-
E.
extendedIn
Indicates that one entity continues, prolongs, or expands the scope, duration, or range of another entity.
- 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_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 9:08 p.m.