Triple
T9677130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Animagic |
E234183
|
entity |
| Predicate | visualStyleCharacteristic |
P61564
|
FINISHED |
| Object | stylized character designs |
—
|
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: stylized character designs | Statement: [Animagic, visualStyleCharacteristic, stylized character designs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visualStyleCharacteristic Context triple: [Animagic, visualStyleCharacteristic, stylized character designs]
-
A.
structuralStyle
Indicates the architectural or design style that characterizes the structure or form of an entity.
-
B.
stylingFeature
Indicates a visual or design-related characteristic applied to an entity, such as formatting, layout, or aesthetic treatment.
-
C.
featuresStyle
Indicates that one entity exhibits, incorporates, or is characterized by a particular style associated with another entity.
-
D.
characterStyle
Indicates how a character is visually or typographically presented, such as its font, weight, size, or decorative attributes.
-
E.
typicalVisualStyle
chosen
Indicates the characteristic or commonly observed visual appearance or aesthetic style associated with an entity.
- 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_69ca84c99e34819092e5563a7106cfca |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9c99ee0481908ead5f7112117c90 |
completed | April 1, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b5d40c8190850ad7a351445f32 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:16 p.m.