Triple
T20123871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Used To |
E490690
|
entity |
| Predicate | hasRecordLabelType |
P121783
|
FINISHED |
| Object | independent record label |
—
|
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: independent record label | Statement: [I Used To, hasRecordLabelType, independent record label]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecordLabelType Context triple: [I Used To, hasRecordLabelType, independent record label]
-
A.
hasRecordLabel
Indicates that an entity (typically a musical artist or release) is associated with or signed to a particular record label.
-
B.
hasRecordType
Indicates that an entity is associated with or classified under a specific type or category of record.
-
C.
hasRecordingLabel
Indicates that an entity (such as an artist or release) is associated with a particular recording label that publishes or distributes its music.
-
D.
hasPublishingLabelType
chosen
Indicates the type or category of publishing label associated with an entity.
-
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_69da62651a0c8190a3e05e95e056a66b |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e6674054188190a15d55a73e86d143 |
completed | April 20, 2026, 5:49 p.m. |
| PD | Predicate disambiguation | batch_69e54cfb0d0081908e789b9b57e96668 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:30 p.m.