Triple
T26296512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jupiter’s magnetosphere |
E661432
|
entity |
| Predicate | plasmaSource |
P160216
|
FINISHED |
| Object | Io’s volcanic gases |
—
|
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: Io’s volcanic gases | Statement: [Jupiter’s magnetosphere, plasmaSource, Io’s volcanic gases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plasmaSource Context triple: [Jupiter’s magnetosphere, plasmaSource, Io’s volcanic gases]
-
A.
plasmaCurrentDesign
Indicates a design relationship in which an entity specifies or defines the intended characteristics or configuration of a plasma current.
-
B.
typicalPlasmaCurrent
Indicates the usual or characteristic electric current flowing through a plasma under standard or expected conditions.
-
C.
usedInPlasmaPhysics
Indicates that something is employed, applied, or serves a role within the field or context of plasma physics.
-
D.
primaryBeamSource
Indicates that an entity serves as the originating source of a primary beam used or produced by another entity.
-
E.
ionizingSource
Indicates that the subject acts as a source that produces or emits ionizing radiation affecting the object.
- 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_69ee812cd48c81908054068f545f0526 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60eaea1d08190b93b85590b8c9781 |
completed | May 2, 2026, 2:48 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f5ffc6268c8190b63f6360ebadab73 |
completed | May 2, 2026, 1:44 p.m. |
Created at: April 26, 2026, 10:12 p.m.