Triple
T23908797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ITER project |
E601277
|
entity |
| Predicate | designedPlasmaCurrent |
P130545
|
FINISHED |
| Object | about 15 megaamperes |
—
|
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: about 15 megaamperes | Statement: [ITER project, designedPlasmaCurrent, about 15 megaamperes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedPlasmaCurrent Context triple: [ITER project, designedPlasmaCurrent, about 15 megaamperes]
-
A.
typicalPlasmaCurrent
Indicates the usual or characteristic electric current flowing through a plasma under standard or expected conditions.
-
B.
plasmaCurrentDesign
chosen
Indicates a design relationship in which an entity specifies or defines the intended characteristics or configuration of a plasma current.
-
C.
beamCurrent
Indicates the amount of electric current carried by a directed beam (such as a particle or electron beam) in a system or experiment.
-
D.
usedInPlasmaPhysics
Indicates that something is employed, applied, or serves a role within the field or context of plasma physics.
-
E.
magneticConfinementType
Indicates the method or scheme of magnetic confinement used to contain a plasma or charged particles.
- 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_69e295364a488190bcac702e9bb7f764 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1ce92e7688190ac421570e0d6a942 |
completed | April 29, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:37 p.m.