Triple
T37899938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Mallory |
E945381
|
entity |
| Predicate | musicComposerOfWorkAppearedIn |
P32102
|
FINISHED |
| Object | Ennio Morricone |
E32312
|
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: Ennio Morricone | Statement: [John Mallory, musicComposerOfWorkAppearedIn, Ennio Morricone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicComposerOfWorkAppearedIn Context triple: [John Mallory, musicComposerOfWorkAppearedIn, Ennio Morricone]
-
A.
musicComposer
chosen
Indicates that one entity is the creator or writer of a piece of music associated with another entity.
-
B.
composedForMusicBy
Indicates that a musical work was specifically created or written by a particular composer.
-
C.
soundtrackComposerCollaboratedWith
Indicates that a soundtrack composer worked together with another person or entity in creating or producing a soundtrack.
-
D.
musicComposedIn
Indicates that a piece of music was created or composed in a specific place or location.
-
E.
workComposer
Indicates that one entity is the composer or creator of a musical or artistic work represented by the other entity.
- 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_69f76ef0e8708190987c7254ed8c7abe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe831c97c88190b27ecf100e25c2a0 |
completed | May 9, 2026, 12:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a410cc4c7c881908926c9cf3e2e76d1 |
completed | June 28, 2026, noon |
| PD | Predicate disambiguation | batch_69fe7f1b92648190b14e56bcaee5d0ca |
completed | May 9, 2026, 12:26 a.m. |
Created at: May 3, 2026, 4:19 p.m.