Triple
T15267319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cray XK7 |
E364932
|
entity |
| Predicate | parallelProgrammingModel |
P107164
|
FINISHED |
| Object | MPI |
—
|
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: MPI | Statement: [Cray XK7, parallelProgrammingModel, MPI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parallelProgrammingModel Context triple: [Cray XK7, parallelProgrammingModel, MPI]
-
A.
supportsParallelProgrammingModel
Indicates that one entity provides facilities or mechanisms enabling the use of a parallel programming model with another entity.
-
B.
hasProgrammingModel
chosen
Indicates that one entity defines, specifies, or is associated with the programming model used or supported by another entity.
-
C.
parallel
Indicates that two or more entities maintain a constant separation and direction without intersecting or converging.
-
D.
distributedProgram
Indicates that an entity is responsible for handing out, circulating, or otherwise making a program (such as an agenda, schedule, or software package) available to others.
-
E.
hasParallelImplementation
Indicates that one implementation of a function, process, or algorithm has a corresponding version designed to run in parallel.
- 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0094ca9ac8190a1f97a7b74c96cd5 |
completed | April 15, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69deca90739081909bd1b797cdb8af2b |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:14 a.m.