Triple
T27777769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sure (music video) |
E699243
|
entity |
| Predicate | recordLabelOfSingle |
P25080
|
FINISHED |
| Object | RCA Records |
—
|
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: RCA Records | Statement: [Sure (music video), recordLabelOfSingle, RCA Records]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordLabelOfSingle Context triple: [Sure (music video), recordLabelOfSingle, RCA Records]
-
A.
recordLabelForSingle
chosen
Indicates that a record label is responsible for producing, releasing, or distributing a particular single.
-
B.
recordLabelAssociated
Indicates that one entity (typically an artist or release) is or has been signed to, released under, or otherwise officially affiliated with a particular record label.
-
C.
recordLabelForCover
Indicates that a particular record label is responsible for releasing or producing a specific cover version of a work.
-
D.
recordLabelForNotableRecording
Indicates that a record label is responsible for producing, releasing, or prominently associated with a particular notable recording.
-
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_69ef6a4b5a9081909c9111396c2be3d2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 27, 2026, 5:07 p.m.