Triple
T15578841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sidestepper |
E374440
|
entity |
| Predicate | movementAxis |
P56811
|
FINISHED |
| Object | horizontal |
—
|
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: horizontal | Statement: [Sidestepper, movementAxis, horizontal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movementAxis Context triple: [Sidestepper, movementAxis, horizontal]
-
A.
movementDirection
Indicates the direction or path along which an entity moves or is moving relative to a reference frame or point.
-
B.
movementSystem
Indicates a relationship where an entity is part of, uses, or is governed by a particular system that enables or controls its movement.
-
C.
transportAxis
chosen
Indicates a directional path or axis along which something is transported or moved from one location to another.
-
D.
movementContext
Indicates the situational or environmental conditions under which a movement or motion event occurs, such as its manner, setting, or constraints.
-
E.
movementAcross
Indicates movement of an entity from one side or area to another, traversing through or over an intervening space or boundary.
- 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_69d85ccd575081908909b71a3f3e3a61 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e24064c8190b132c3092877fbfa |
completed | April 16, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69deda817e9881909b0c66fc9056f7d5 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:11 a.m.