Triple
T16879159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fight the Power |
E421372
|
entity |
| Predicate | recordLabelAtRelease |
P25080
|
FINISHED |
| Object | Motown for soundtrack single |
—
|
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: Motown for soundtrack single | Statement: [Fight the Power, recordLabelAtRelease, Motown for soundtrack single]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordLabelAtRelease Context triple: [Fight the Power, recordLabelAtRelease, Motown for soundtrack single]
-
A.
recordLabelForSingle
chosen
Indicates that a record label is responsible for producing, releasing, or distributing a particular single.
-
B.
recordLabelForNotableRecording
Indicates that a record label is responsible for producing, releasing, or prominently associated with a particular notable recording.
-
C.
recordLabelLocation
Indicates the geographic place where a record label is based or operates from.
-
D.
recordLabelCatalogNumber
Indicates the catalog or identification number assigned to a release by a record label.
-
E.
ownedRecordLabel
Indicates that one entity previously possessed legal ownership or controlling interest in a particular record label.
- 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_69d889d470fc8190b4aec199636c0c56 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3b7f9aea0819090aef3c0c1ad349d |
completed | April 18, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69e32b90ec3c819099c51bb7baf2984c |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:29 a.m.