Triple
T34232560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Don Omar: Live in Miami |
E878241
|
entity |
| Predicate | featuresMusicalWorkCreator |
P20942
|
FINISHED |
| Object | Don Omar |
E249441
|
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: Don Omar | Statement: [Don Omar: Live in Miami, featuresMusicalWorkCreator, Don Omar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresMusicalWorkCreator Context triple: [Don Omar: Live in Miami, featuresMusicalWorkCreator, Don Omar]
-
A.
artistOf
Indicates that one entity is the creator or performer responsible for producing a particular work or piece.
-
B.
hasMusicalArtistRoleOfCreator
Indicates that the specified musical artist serves as the creator (e.g., composer, originator) of the referenced musical work or content.
-
C.
composerOfCataloguedWork
Indicates that one entity is the composer or creator of a specific catalogued musical or artistic work associated with another entity.
-
D.
featuresMusician
chosen
Indicates that something (such as a work, event, or recording) prominently includes or showcases a particular musician.
-
E.
featuresSongwriter
Indicates that a musical work includes or credits a particular person as its songwriter.
- 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_69f349b22d8c819096b22df268382aa9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a030d3db2748190b32fcf7b21bd0d0a |
completed | May 12, 2026, 11:21 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3840109cf8819089151d143da2e4e9 |
completed | June 21, 2026, 7:48 p.m. |
| PD | Predicate disambiguation | batch_6a030ca6bf388190b2f6931376323da3 |
completed | May 12, 2026, 11:19 a.m. |
Created at: May 1, 2026, 1:56 a.m.