Triple
T23908824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ITER project |
E601277
|
entity |
| Predicate | plasmaConfinementMethod |
P145787
|
FINISHED |
| Object | magnetic confinement |
—
|
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: magnetic confinement | Statement: [ITER project, plasmaConfinementMethod, magnetic confinement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plasmaConfinementMethod Context triple: [ITER project, plasmaConfinementMethod, magnetic confinement]
-
A.
magneticConfinementType
chosen
Indicates the method or scheme of magnetic confinement used to contain a plasma or charged particles.
-
B.
typicalPlasmaCurrent
Indicates the usual or characteristic electric current flowing through a plasma under standard or expected conditions.
-
C.
confinementMethod
Indicates the method or means by which an entity is confined, restrained, or kept in captivity.
-
D.
usedInPlasmaPhysics
Indicates that something is employed, applied, or serves a role within the field or context of plasma physics.
-
E.
confinementRegime
Indicates the specific conditions or restrictions under which an entity is confined or held.
- 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.