Triple
T15625773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eska |
E375671
|
entity |
| Predicate | bendingSubskill |
P119495
|
FINISHED |
| Object | ice manipulation |
—
|
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: ice manipulation | Statement: [Eska, bendingSubskill, ice manipulation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bendingSubskill Context triple: [Eska, bendingSubskill, ice manipulation]
-
A.
bendAngle
Indicates the degree to which one part is bent relative to another, typically measured as the angle formed at their joint or intersection.
-
B.
bendLocation
Indicates the location at which something bends, curves, or changes direction.
-
C.
techniqueRequired
Indicates that performing one entity (such as an action, process, or task) necessitates the use of a specific technique associated with the other entity.
-
D.
bentName
Indicates that an entity’s name is misspelled, malformed, or otherwise incorrectly rendered relative to its correct or standard form.
-
E.
hasTechnique
Indicates that an entity employs, utilizes, or is associated with a particular method, procedure, or technique.
- 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_69d85cd035a48190b73d5579ab73969a |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e9e5e248190ae54cda1fde51efb |
completed | April 16, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69deda868d4481908f4bce1c64d2902a |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f3016c8190ac68d76e65e07af4 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:14 a.m.