Triple
T26692022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | P-waves |
E672911
|
entity |
| Predicate | particleMotionDirection |
P16306
|
FINISHED |
| Object | parallel to direction of wave propagation |
—
|
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: parallel to direction of wave propagation | Statement: [P-waves, particleMotionDirection, parallel to direction of wave propagation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: particleMotionDirection Context triple: [P-waves, particleMotionDirection, parallel to direction of wave propagation]
-
A.
movementDirection
chosen
Indicates the direction or path along which an entity moves or is moving relative to a reference frame or point.
-
B.
modelsMotionOf
Indicates that one entity provides a representation or simulation of the motion or movement behavior of another entity.
-
C.
dispersionDirection
Indicates the direction in which something spreads, scatters, or disperses from its source.
-
D.
relativeMotionType
Indicates the type or nature of motion occurring between two entities relative to one another.
-
E.
containsDirectionOf
Indicates that one entity includes or encompasses the directional orientation or path associated with 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_69eecda2066c8190a344218afa5e89c1 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 27, 2026, 3:26 a.m.