Triple
T2033564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upkeep bouncing bomb |
E44570
|
entity |
| Predicate | spinDirection |
P7284
|
FINISHED |
| Object | backspin |
—
|
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: backspin | Statement: [Upkeep bouncing bomb, spinDirection, backspin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spinDirection Context triple: [Upkeep bouncing bomb, spinDirection, backspin]
-
A.
offsetDirection
Indicates the relative direction in which one entity is displaced or shifted from another reference entity.
-
B.
rotationType
chosen
Indicates the specific kind or mode of rotational movement or orientation applied in a given context.
-
C.
shaftOrientation
Indicates the directional alignment or angle at which a shaft is positioned or oriented relative to a reference frame or object.
-
D.
spinRate
Indicates the rotational speed at which an object or system is spinning, typically measured as revolutions per unit time.
-
E.
movementDirection
Indicates the direction or path along which an entity moves or is moving relative to a reference frame or point.
- 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_69a889144f2481909932f0746a93023d |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb93255248190bd47a54a7b3c7447 |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb7a8125881909c0cb58b777c1faa |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:39 p.m.