Triple
T38545474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aladdin: Original Motion Picture Soundtrack |
E924951
|
entity |
| Predicate | featuresCharacterVoices |
P161313
|
FINISHED |
| Object | Genie |
E347351
|
NE 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: Genie | Statement: [Aladdin: Original Motion Picture Soundtrack, featuresCharacterVoices, Genie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresCharacterVoices Context triple: [Aladdin: Original Motion Picture Soundtrack, featuresCharacterVoices, Genie]
-
A.
characterVoiceCasting
Indicates the assignment of a specific voice actor or voice performance to a particular character.
-
B.
characterTypeVoiced
Indicates that one character serves as the voice actor or vocal performer for another character.
-
C.
voiceCharacter
chosen
Indicates that one entity provides the voice for, or vocally portrays, a particular character in a work.
-
D.
hasVoiceActing
Indicates that one entity provides voice performance for a character, role, or work associated with another entity.
-
E.
voiceActorCharacter
Indicates that a person serving as a voice actor provides the voice for a particular character.
- F. None of above.
Provenance (4 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_69f76eadeac081909cdfdd0474cb6765 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41e037ff9081908f46513ae0253650 |
completed | June 29, 2026, 3:02 a.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.