Triple
T13644606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toy Soldiers Parachute Drop |
E326069
|
entity |
| Predicate | dropStyle |
P110952
|
FINISHED |
| Object | gentle bouncing drop sequence |
—
|
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: gentle bouncing drop sequence | Statement: [Toy Soldiers Parachute Drop, dropStyle, gentle bouncing drop sequence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dropStyle Context triple: [Toy Soldiers Parachute Drop, dropStyle, gentle bouncing drop sequence]
-
A.
dropType
Indicates the manner or category of how something is dropped, released, or caused to fall.
-
B.
dropSource
Indicates that an entity serves as the origin or starting point from which something is dropped, released, or caused to fall.
-
C.
dropsSet
Indicates that a set of items or rewards is released, yielded, or made available as a result of a particular event, action, or condition.
-
D.
drop
Indicates that an entity causes something to fall or be released from a higher position to a lower one.
-
E.
renouncedStyle
Indicates that an entity has formally given up or abandoned a particular style it previously used or was associated with.
- F. None of above. chosen
Provenance (4 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_69d8076beddc8190a53156f5bea77f5e |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc60635d08190899806fe8936f02a |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8a027081908d8f884b89707a5e |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59ca1a88190a6abd3bd00554c93 |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 9:51 p.m.