Triple
T32329133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paquita |
E825998
|
entity |
| Predicate | musicAddedBy |
P192786
|
FINISHED |
| Object | Ludwig Minkus |
—
|
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: Ludwig Minkus | Statement: [Paquita, musicAddedBy, Ludwig Minkus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicAddedBy Context triple: [Paquita, musicAddedBy, Ludwig Minkus]
-
A.
musicAddedIn
Indicates that music was incorporated or introduced into something (such as a work, event, or medium) at a particular time or in a particular context.
-
B.
musicAdaptedBy
Indicates that a piece of music has been modified, arranged, or reworked by a particular person or entity from an existing original.
-
C.
musicBy
Indicates that a piece of music, performance, or recording is created, composed, or performed by a specified musical artist or group.
-
D.
musicCompiledBy
Indicates that a musical work, collection, or recording has been assembled, selected, or put together by a specified compiler.
-
E.
alsoAttributedMusicTo
Indicates that additional musical works or contributions are credited to the same entity beyond those already specified.
- F. None of above. chosen
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_69f34912d0c48190bba75770660320e9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
| PDg | Predicate description generation | batch_69fd2a2095f88190bfcbcb2973516ffc |
completed | May 8, 2026, 12:11 a.m. |
Created at: May 1, 2026, 12:47 a.m.