Triple
T36871205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kirby calculus |
E911226
|
entity |
| Predicate | hasMove |
P109912
|
FINISHED |
| Object | handle slide |
—
|
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: handle slide | Statement: [Kirby calculus, hasMove, handle slide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMove Context triple: [Kirby calculus, hasMove, handle slide]
-
A.
hasMoveType
Indicates that an action or move is associated with a specific type or category (such as elemental, functional, or classification-based).
-
B.
canMove
Indicates that one entity has the ability or permission to change its location or position relative to its environment or another entity.
-
C.
hasMovementLegacy
Indicates that an entity carries forward, preserves, or significantly influences the ongoing impact, traditions, or ideals of a particular movement.
-
D.
hasMovementBefore
Indicates that one movement or motion event occurs earlier in time than another movement or motion event.
-
E.
usesMove
chosen
Indicates that an entity performs or executes a specific move or action.
- 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_69f76e82339881909607a65c0503d941 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff7ae5d088819089aa3b6360b6b749 |
completed | May 9, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69ff7a4df6488190bf60d675b36b1d6d |
completed | May 9, 2026, 6:17 p.m. |
Created at: May 3, 2026, 4:13 p.m.