Triple
T19727169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cybermedia Center (Osaka University) |
E473756
|
entity |
| Predicate | computingResourceType |
P137098
|
FINISHED |
| Object | supercomputer |
—
|
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: supercomputer | Statement: [Cybermedia Center (Osaka University), computingResourceType, supercomputer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: computingResourceType Context triple: [Cybermedia Center (Osaka University), computingResourceType, supercomputer]
-
A.
computingModel
Indicates the computational framework, paradigm, or formal system used to perform or describe a computation.
-
B.
computingCenter
Indicates that an entity functions as or is associated with a computing center, i.e., a facility or unit where computing resources and services are provided or managed.
-
C.
acceleratorType
Indicates the kind or category of accelerator associated with or used by an entity.
-
D.
typeOfCloud
Indicates the specific category or classification of a cloud within a cloud-type taxonomy or system.
-
E.
virtualizationType
Indicates the specific method or technology by which a resource, system, or environment is virtualized.
- F. None of above. chosen
Provenance (4 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_69d8e517ebd48190979ee76723bcfadf |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e649f95d5c8190858ba414ff3e95a8 |
completed | April 20, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69e5304a7aac8190ac13f75f0c008e45 |
completed | April 19, 2026, 7:43 p.m. |
| PDg | Predicate description generation | batch_69e532bbedf081908d801600e2af94a7 |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:47 p.m.