Triple
T17713299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AWAKE Run 1 experiments |
E441623
|
entity |
| Predicate | usesPlasmaSource |
P75634
|
FINISHED |
| Object | rubidium vapor plasma source |
—
|
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: rubidium vapor plasma source | Statement: [AWAKE Run 1 experiments, usesPlasmaSource, rubidium vapor plasma source]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPlasmaSource Context triple: [AWAKE Run 1 experiments, usesPlasmaSource, rubidium vapor plasma source]
-
A.
advantageOverPlasma
Indicates that one entity possesses a benefit, superiority, or favorable property when compared specifically to plasma.
-
B.
usedInPlasmaPhysics
chosen
Indicates that something is employed, applied, or serves a role within the field or context of plasma physics.
-
C.
hasPowerSource
Indicates that an entity derives its operational energy or functionality from a specified power source.
-
D.
sourceOfPower
Indicates that one entity serves as the origin or provider of power, energy, or authority for another entity.
-
E.
hasCoolingSource
Indicates that one entity provides or serves as a cooling source for another entity.
- 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_69d8b9ea20b48190ace88bb46b01e6a9 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4729cebd08190872be96a26d0f7ce |
completed | April 19, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69e3cde601d4819097903f471f1fe99a |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:06 a.m.