Triple
T32066116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tinny |
E818885
|
entity |
| Predicate | hasAppearanceStyle |
P1609
|
FINISHED |
| Object | early Pixar CGI aesthetic |
—
|
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: early Pixar CGI aesthetic | Statement: [Tinny, hasAppearanceStyle, early Pixar CGI aesthetic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAppearanceStyle Context triple: [Tinny, hasAppearanceStyle, early Pixar CGI aesthetic]
-
A.
hasStyle
chosen
Indicates that an entity possesses, exhibits, or is characterized by a particular style or manner.
-
B.
hasMediaAppearanceIn
Indicates that an entity appears or is featured as media content within a specified media work, program, or publication.
-
C.
hasPowerStyle
Indicates that one entity possesses or exhibits a particular style or manner of using power in relation to another entity or context.
-
D.
givesAppearanceTo
Indicates that one entity imparts or determines the visual look or outward appearance of another entity.
-
E.
hasVariableAppearance
Indicates that an entity’s appearance can change or differ across instances, contexts, or over time rather than remaining fixed.
- 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_69f348fecc088190af1470afe5a969f0 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 1, 2026, 12:22 a.m.