Triple
T21818149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASDEX Upgrade |
E538654
|
entity |
| Predicate | magneticConfinementType |
P145787
|
FINISHED |
| Object | toroidal |
—
|
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: toroidal | Statement: [ASDEX Upgrade, magneticConfinementType, toroidal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: magneticConfinementType Context triple: [ASDEX Upgrade, magneticConfinementType, toroidal]
-
A.
neutronFluxType
Indicates the specific classification or category of neutron flux characterizing how neutrons are distributed or behave in a given context.
-
B.
reactorType
Indicates the specific kind or category of reactor associated with an entity.
-
C.
fuelAssemblyType
Indicates the specific design or classification of a fuel assembly associated with an entity.
-
D.
usesMagnetType
Indicates that one entity employs or operates with a specific type of magnet in its function or configuration.
-
E.
thermalNeutronReactor
Indicates that the subject is a nuclear reactor that operates using thermal (low-energy) neutrons to sustain its fission chain reaction.
- 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_69e0c475038c8190abb9b1a20eb8ff50 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f07ccd0d908190a43af4fcc7d6ca03 |
completed | April 28, 2026, 9:24 a.m. |
| PD | Predicate disambiguation | batch_69e6be815a108190be81d7c987d0c0d6 |
completed | April 21, 2026, 12:02 a.m. |
| PDg | Predicate description generation | batch_69e6c670ee608190b9cfdc09de74f0de |
completed | April 21, 2026, 12:36 a.m. |
Created at: April 16, 2026, 6:54 p.m.