Triple
T27607703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Emperor’s New Groove |
E700224
|
entity |
| Predicate | hasComposerOrArranger |
P4873
|
FINISHED |
| Object | David Hartley |
—
|
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: David Hartley | Statement: [The Emperor’s New Groove, hasComposerOrArranger, David Hartley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComposerOrArranger Context triple: [The Emperor’s New Groove, hasComposerOrArranger, David Hartley]
-
A.
hasArranger
chosen
Indicates that one entity serves as the arranger (e.g., musically or structurally) for another entity, such as a work, performance, or composition.
-
B.
hasMusicalComposer
Indicates that one entity serves as the musical composer responsible for creating the music associated with another entity.
-
C.
hasCoComposer
Indicates that an entity shares authorship of a musical composition with one or more other composers.
-
D.
hasMainComposerRole
Indicates that an entity holds the primary or leading composer role for a given work or production.
-
E.
hasGenreAsComposer
Indicates that an entity, in its role as a composer, is associated with a specific musical or artistic genre.
- 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_69ef6a4e2e208190b63b7268f405785c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69ff1f3f94fc819095955299f50ab4ce |
completed | May 9, 2026, 11:49 a.m. |
| PD | Predicate disambiguation | batch_69ff1ea47748819082f63d9b9d9c3e65 |
completed | May 9, 2026, 11:46 a.m. |
Created at: April 27, 2026, 2:10 p.m.