Triple
T32146812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Inventor |
E821043
|
entity |
| Predicate | featuresAnimationTechnique |
P136011
|
FINISHED |
| Object | stop-motion |
—
|
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: stop-motion | Statement: [The Inventor, featuresAnimationTechnique, stop-motion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresAnimationTechnique Context triple: [The Inventor, featuresAnimationTechnique, stop-motion]
-
A.
featuresAnimation
Indicates that something includes or prominently presents an animation as part of its content or functionality.
-
B.
animationTechnology
chosen
Indicates a relationship where one entity uses, is created with, or is characterized by a particular animation technology.
-
C.
featuresTechnique
Indicates that something incorporates or makes use of a particular technique as part of its content or execution.
-
D.
specialEffectsTechnique
Indicates a relationship where a particular special effects method or process is used to create or enhance visual or auditory effects in a production.
-
E.
artisticTechnique
Indicates the method, style, or process used to create or execute an artistic work.
- 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_69f3490520d081909b2f1271dab75faa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a00b8e0a5508190abc5c1e492bed12e |
completed | May 10, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_6a00b8327d048190850af317f60f0f8b |
completed | May 10, 2026, 4:54 p.m. |
Created at: May 1, 2026, 12:31 a.m.