Triple
T25602552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reed–Solomon codes |
E641825
|
entity |
| Predicate | minimumDistanceFormula |
P159156
|
FINISHED |
| Object | d = n - k + 1 |
—
|
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: d = n - k + 1 | Statement: [Reed–Solomon codes, minimumDistanceFormula, d = n - k + 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minimumDistanceFormula Context triple: [Reed–Solomon codes, minimumDistanceFormula, d = n - k + 1]
-
A.
minimumDistanceSymbol
Indicates the symbol or notation used to represent the minimum distance between two or more entities.
-
B.
bestDistance
Indicates the smallest or most optimal distance value achieved or applicable between entities in a given context.
-
C.
distanceMetric
Indicates a quantitative measure of how far apart two entities are within a given space or according to a specified metric.
-
D.
numberOfDistances
Indicates the count of distinct distance values associated with or measured between entities in a given context.
-
E.
distancedFrom
Indicates that one entity is physically or metaphorically kept at a certain distance or separation from another entity.
- 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_69e75dc6ccf081908d49578fd36a76d5 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f9a7d7d881909014fdf3746f981b |
completed | May 2, 2026, 1:18 p.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 21, 2026, 4:36 p.m.