Triple
T26982507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alfvén waves |
E679640
|
entity |
| Predicate | groupVelocity |
P161124
|
FINISHED |
| Object | Alfvén speed |
—
|
NE NERFINISHED |
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: Alfvén speed | Statement: [Alfvén waves, groupVelocity, Alfvén speed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: groupVelocity Context triple: [Alfvén waves, groupVelocity, Alfvén speed]
-
A.
reportedGroupVelocity
Indicates that a group’s velocity has been measured or estimated and formally reported as a value associated with that group.
-
B.
propagationVelocityDependsOn
chosen
Indicates that the propagation velocity of a phenomenon is determined or influenced by another specified factor or set of factors.
-
C.
symbolForVelocity
Indicates that one entity is used as the symbolic representation or notation for the concept of velocity of another entity.
-
D.
waveLength
Indicates the distance between successive corresponding points (such as peaks) of a wave associated with the related entities.
-
E.
velocityPerturbation
Indicates a change or disturbance in an entity’s velocity relative to some reference or baseline motion.
- 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f631850ae08190a0ba51e4f1e4ccb3 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 6:46 a.m.