Triple
T33293363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moody's Mood |
E852374
|
entity |
| Predicate | originalCompositionBy |
P140035
|
FINISHED |
| Object | James Moody |
E913723
|
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: James Moody | Statement: [Moody's Mood, originalCompositionBy, James Moody]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalCompositionBy Context triple: [Moody's Mood, originalCompositionBy, James Moody]
-
A.
originalComposition
Indicates that one entity is the initial or first-created version from which another entity (such as an adaptation, translation, or derivative work) is derived.
-
B.
originalCompilation
Indicates that one work is the initial or primary compilation from which another compiled or derived version originates.
-
C.
originalSong
Indicates that one entity is the source or initial version of a song from which another entity (such as a cover, remix, or adaptation) is derived.
-
D.
composerOfOriginalSongs
chosen
Indicates that one entity is the composer who created the original songs associated with another entity.
-
E.
laterComposition
Indicates that one composition was created after another in time.
- 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_69f349660ff48190a4568803d0b89941 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a030c7d03308190a102689db1e8b657 |
completed | May 12, 2026, 11:18 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a35a65890ac8190bd0ecabd3ba64c76 |
completed | June 19, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_6a030a57b16c81909191270f64a77fcf |
completed | May 12, 2026, 11:09 a.m. |
Created at: May 1, 2026, 1:33 a.m.