Triple
T26692075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stoneley waves |
E672912
|
entity |
| Predicate | haveMotionType |
P23273
|
FINISHED |
| Object | predominantly longitudinal |
—
|
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: predominantly longitudinal | Statement: [Stoneley waves, haveMotionType, predominantly longitudinal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveMotionType Context triple: [Stoneley waves, haveMotionType, predominantly longitudinal]
-
A.
hasMovementType
chosen
Indicates the type or mode of movement associated with an entity, such as how it moves or is transported.
-
B.
hasMoveType
Indicates that an action or move is associated with a specific type or category (such as elemental, functional, or classification-based).
-
C.
hasVerticalMotion
Indicates that an entity is undergoing or exhibiting motion in the vertical direction (upward or downward).
-
D.
hasAnimationType
Indicates the specific style or method of animation applied to an entity or its visual content.
-
E.
includesMovementType
Indicates that one entity encompasses or contains a specific type or category of movement 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_69f6174310d48190b1ef1e515fed7990 |
completed | May 2, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:26 a.m.