Triple
T38262796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Echternach dancing procession |
E1017972
|
entity |
| Predicate | hasMainTypeOfMovement |
P189991
|
FINISHED |
| Object | hopping step |
—
|
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: hopping step | Statement: [Echternach dancing procession, hasMainTypeOfMovement, hopping step]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainTypeOfMovement Context triple: [Echternach dancing procession, hasMainTypeOfMovement, hopping step]
-
A.
hasMovementType
Indicates the type or mode of movement associated with an entity, such as how it moves or is transported.
-
B.
isMovementOfType
chosen
Indicates that a movement or motion event belongs to, or can be classified under, a specific type or category of movement.
-
C.
hasMoveType
Indicates that an action or move is associated with a specific type or category (such as elemental, functional, or classification-based).
-
D.
includesMovementType
Indicates that one entity encompasses or contains a specific type or category of movement associated with another entity.
-
E.
isMovementOf
Indicates that one entity represents the motion, relocation, or change of position of 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_69f76de33e4481909099fa812709bd42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:30 p.m.