Triple
T6741200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lokomotiv |
E154084
|
entity |
| Predicate | movesBy |
P70363
|
FINISHED |
| Object | adhesion between wheels and rails |
—
|
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: adhesion between wheels and rails | Statement: [Lokomotiv, movesBy, adhesion between wheels and rails]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movesBy Context triple: [Lokomotiv, movesBy, adhesion between wheels and rails]
-
A.
movedBy
Indicates that an entity changes position or location as a result of another entity’s action or influence.
-
B.
motionBy
chosen
Indicates that one entity undergoes movement or change in position caused or driven by another entity or agent.
-
C.
movesRelativeTo
Indicates that one entity changes its position or orientation with respect to another entity, rather than with respect to a fixed reference frame.
-
D.
movementIn
Indicates a relationship where an entity moves within, into, or inside a specified area, space, or container.
-
E.
movementFor
Indicates that one entity moves on behalf of, in support of, or as a representative action 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_69c6880d84d8819095d19de2295f26ac |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d18971e081908372cd25d52a11bd |
completed | March 27, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69c6d09067a0819087ed6c820f4699f8 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:10 p.m.