Triple
T23908553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KSTAR |
E601270
|
entity |
| Predicate | magnetTechnology |
P3957
|
FINISHED |
| Object | niobium-tin superconductors |
—
|
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: niobium-tin superconductors | Statement: [KSTAR, magnetTechnology, niobium-tin superconductors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: magnetTechnology Context triple: [KSTAR, magnetTechnology, niobium-tin superconductors]
-
A.
usesMagnetType
chosen
Indicates that one entity employs or operates with a specific type of magnet in its function or configuration.
-
B.
magneticActivity
Indicates a relationship where an entity exhibits, causes, or is characterized by magnetic phenomena such as fields, storms, or fluctuations.
-
C.
magnetizationArisesFrom
Indicates that a magnetization property or state is caused or generated by a specified underlying process, structure, or source.
-
D.
magneticInteraction
Indicates a relationship in which entities exert forces or influences on each other due to their magnetic fields or magnetic properties.
-
E.
hasMagneticMoment
Indicates that an entity possesses a magnetic moment, characterizing the strength and orientation of its magnetism.
- 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.