Triple
T26894961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andreas Deja |
E677874
|
entity |
| Predicate | supervisingAnimatorOf |
P77788
|
FINISHED |
| Object | Gaston |
—
|
NE NERFINISHED |
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: Gaston | Statement: [Andreas Deja, supervisingAnimatorOf, Gaston]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supervisingAnimatorOf Context triple: [Andreas Deja, supervisingAnimatorOf, Gaston]
-
A.
animator
Indicates that one entity serves as the animator or creator of animated content for another entity or work.
-
B.
isAnimatedBy
Indicates that an entity’s motion or behavior is driven, controlled, or brought to life by another entity or process.
-
C.
supervisesBy
Indicates that one entity is overseen, directed, or managed under the authority of another entity.
-
D.
supervisesFor
Indicates that one entity oversees, directs, or manages the work, activities, or responsibilities of another entity on behalf of a third party or specific purpose.
-
E.
leadAnimator
chosen
Indicates that one entity serves as the primary or supervising animator responsible for leading the animation work on another entity (such as a project, scene, or production).
- 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_69eee9befee48190a26f214faa867be7 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 27, 2026, 5:47 a.m.