Triple
T31025297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hopper |
E790551
|
entity |
| Predicate | supportsComputationType |
P24486
|
FINISHED |
| Object | FP64 |
—
|
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: FP64 | Statement: [Hopper, supportsComputationType, FP64]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsComputationType Context triple: [Hopper, supportsComputationType, FP64]
-
A.
usesComputationMethod
Indicates that an entity performs its processing or decision-making by applying a specified computational method or algorithm.
-
B.
supportsCalculation
Indicates that one entity provides the capability or functionality for another entity to perform a specific calculation or set of calculations.
-
C.
supportsType
chosen
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
D.
supportsInferenceOf
Indicates that one entity provides a logical basis or justification for concluding or deriving another entity.
-
E.
supportsTargetType
Indicates that one entity is capable of operating with, handling, or being compatible with a specified target type.
- 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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:58 p.m.