Triple
T26253888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | extended binary Golay code |
E656668
|
entity |
| Predicate | meetsBound |
P68117
|
FINISHED |
| Object | sphere-packing bound for t = 3 |
—
|
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: sphere-packing bound for t = 3 | Statement: [extended binary Golay code, meetsBound, sphere-packing bound for t = 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meetsBound Context triple: [extended binary Golay code, meetsBound, sphere-packing bound for t = 3]
-
A.
meetsTo
Indicates that one entity comes together with another at a specific time and place for an encounter, appointment, or interaction.
-
B.
hasBoundaryCriterion
chosen
Indicates that something is associated with a specific rule or condition used to define or limit its boundary.
-
C.
meets
Indicates that two or more entities come together at the same place and time, typically for interaction or a shared purpose.
-
D.
meetsCurrent
Indicates that an entity currently satisfies or fulfills a specified condition, requirement, or standard.
-
E.
meetsType
Indicates that one entity encounters or comes into contact with another entity in a particular manner or context.
- 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.