Triple
T26253873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | extended binary Golay code |
E656668
|
entity |
| Predicate | codeRate |
P48288
|
FINISHED |
| Object | 1/2 |
—
|
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: 1/2 | Statement: [extended binary Golay code, codeRate, 1/2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codeRate Context triple: [extended binary Golay code, codeRate, 1/2]
-
A.
exportRate
Indicates the rate or proportion at which goods, services, or resources are sent out from one entity or region to others.
-
B.
rate
Indicates the numerical evaluation or assessment assigned by one entity to another based on perceived quality, performance, or value.
-
C.
referenceRate
Indicates that one entity serves as the benchmark or base rate used to determine or adjust the rate applied to another entity or transaction.
-
D.
supportsCodeRates
chosen
Indicates that one entity is capable of handling, processing, or operating at the specific code rates associated with another entity.
-
E.
dataRate
Indicates the rate at which data is transmitted, processed, or transferred between entities over a given time interval.
- 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.