Triple
T16508253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Out ta Get Me |
E400986
|
entity |
| Predicate | hasMusicBrainzWorkId |
P36778
|
FINISHED |
| Object | b3a4a3a0-3a0b-3a4a-9f0b-0f0a3a0b3a4a |
—
|
LITERAL 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: b3a4a3a0-3a0b-3a4a-9f0b-0f0a3a0b3a4a | Statement: [Out ta Get Me, hasMusicBrainzWorkId, b3a4a3a0-3a0b-3a4a-9f0b-0f0a3a0b3a4a]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMusicBrainzWorkId Context triple: [Out ta Get Me, hasMusicBrainzWorkId, b3a4a3a0-3a0b-3a4a-9f0b-0f0a3a0b3a4a]
-
A.
musicBrainzID
chosen
Indicates that an entity is associated with a specific identifier in the MusicBrainz database that uniquely references it.
-
B.
isMusicalWork
Indicates that one entity is a musical composition or piece created as an artistic work.
-
C.
discogsID
Indicates that an entity is associated with a specific identifier used by the Discogs music database to reference it uniquely.
-
D.
hasMusicalWorkType
Indicates that a musical work is associated with a specific type or category of musical composition.
-
E.
hasWorkNumberInBachGesellschaft
Indicates that an entity is assigned a specific work number in the Bach-Gesellschaft (BG) catalog of Bach’s compositions.
- F. None of above.
Provenance (3 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e54331c8190b3c4f9de95cbbc5e |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296902d6c8190884ddb612b8c5b36 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.