Triple
T10026027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skins |
E200725
|
entity |
| Predicate | hasCastRotationBy |
P91774
|
FINISHED |
| Object | generation |
—
|
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: generation | Statement: [Skins, hasCastRotationBy, generation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCastRotationBy Context triple: [Skins, hasCastRotationBy, generation]
-
A.
hasRotationalVelocity
Indicates that an entity is rotating and specifies the rate and direction of its angular motion around an axis.
-
B.
isRotational
Indicates that one entity moves, transforms, or is oriented by rotating around a point, axis, or center relative to another.
-
C.
hasChaoticRotation
Indicates that an object rotates in a highly irregular, unpredictable manner rather than following a stable, consistent spin.
-
D.
rotatesWith
Indicates that two or more entities turn or spin together in a coordinated or mechanically linked manner, typically sharing the same rotational motion or axis.
-
E.
hasRotationCurve
Indicates that an object is associated with a rotation curve describing how its rotational velocity varies with radius or position.
- 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_69ca831c45f08190ac1505cc15076608 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cdcde2009081908eddda7813617df4 |
completed | April 2, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69cd4b7cd4208190b2253583ee2f892c |
completed | April 1, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69cd4f8d9b888190b8067bd916dae773 |
completed | April 1, 2026, 5:02 p.m. |
Created at: March 30, 2026, 8:53 p.m.