Triple
T35959570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K computer |
E1039957
|
entity |
| Predicate | standardBenchmark |
P23745
|
FINISHED |
| Object | LINPACK |
—
|
NE NERFINISHED |
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: LINPACK | Statement: [K computer, standardBenchmark, LINPACK]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardBenchmark Context triple: [K computer, standardBenchmark, LINPACK]
-
A.
primaryBenchmarkProvider
Indicates that one entity serves as the main or default source of benchmark data or performance standards for another entity.
-
B.
benchmarkFor
chosen
Indicates that one entity serves as a standard or reference point against which the performance, quality, or characteristics of another entity are measured or evaluated.
-
C.
baseStandard
Indicates that one entity serves as the foundational or reference standard upon which another entity is defined, measured, or evaluated.
-
D.
standardReference
Indicates that one entity serves as the authoritative or canonical reference or benchmark for interpreting, validating, or comparing another entity.
-
E.
standardExample
Indicates that something is a typical or canonical instance used to illustrate a general case or concept.
- 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_69f76e26b21081909fd9ffb3aff6c77a |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
Created at: May 3, 2026, 4:07 p.m.