Triple
T24180147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rude Mood |
E599396
|
entity |
| Predicate | recordingBand |
P88803
|
FINISHED |
| Object | Double Trouble |
—
|
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: Double Trouble | Statement: [Rude Mood, recordingBand, Double Trouble]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordingBand Context triple: [Rude Mood, recordingBand, Double Trouble]
-
A.
recordingBandFor
chosen
Indicates that a particular musical band is responsible for recording a given musical work, track, or album.
-
B.
recordingOf
Indicates that one entity is an audio or video capture or performance that documents, represents, or preserves another entity (such as a work, event, or expression).
-
C.
recordedByBandMemberOf
Indicates that a recording was made by an individual who is a member of a specified band.
-
D.
recordingFor
Indicates that one entity serves as a recorded representation (such as audio, video, or data capture) created for, or documenting, another entity or event.
-
E.
band
Indicates that multiple entities join together to form a unified group, typically for a shared purpose or activity.
- 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_69e288cca05481908faeb1563711114a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:34 p.m.