Triple
T35959646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Summit |
E1039959
|
entity |
| Predicate | peakPerformancePFLOPS |
P61344
|
FINISHED |
| Object | 200 |
—
|
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: 200 | Statement: [Summit, peakPerformancePFLOPS, 200]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakPerformancePFLOPS Context triple: [Summit, peakPerformancePFLOPS, 200]
-
A.
floatingPointPerformance
Indicates the level of computational capability or efficiency an entity has when performing floating-point arithmetic operations.
-
B.
LINPACKPerformance
chosen
Indicates the level of computational performance achieved by an entity when running the LINPACK benchmark, typically measured in floating-point operations per second.
-
C.
gpuComputePerformance
Indicates the level of processing capability a GPU can deliver for computational tasks, typically measured in operations per unit time.
-
D.
numberOfFloatingPointUnits
Indicates the quantity of floating-point processing units associated with or contained in an entity.
-
E.
top500List
Indicates that an entity is included in a ranking or compilation of the top 500 items within a particular domain or category.
- 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_69f7ac23d1388190bdf9628b294943bd |
completed | May 3, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.