Triple
T38369972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HarmonQuest |
E892549
|
entity |
| Predicate | hasLeadAnimator |
P77788
|
FINISHED |
| Object | Starburns Industries animation team |
—
|
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: Starburns Industries animation team | Statement: [HarmonQuest, hasLeadAnimator, Starburns Industries animation team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLeadAnimator Context triple: [HarmonQuest, hasLeadAnimator, Starburns Industries animation team]
-
A.
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).
-
B.
hasLeader
Indicates that one entity serves as the leader or head of another entity.
-
C.
isAnimatedBy
Indicates that an entity’s motion or behavior is driven, controlled, or brought to life by another entity or process.
-
D.
hasLeadPerformanceBy
Indicates that a work or production features a particular entity as its primary or lead performer.
-
E.
hasLeadInSeries
Indicates that one entity serves as the primary or starring role in a series associated with another 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_69f76e47cb4c8190bdd92cd1db59c0c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fec00f27988190955de6b6348a4d97 |
completed | May 9, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69febd52037c8190b475dbd50fdbc13e |
completed | May 9, 2026, 4:51 a.m. |
Created at: May 3, 2026, 4:31 p.m.