Triple
T16122030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Double Six Records |
E391170
|
entity |
| Predicate | hasBrandRole |
P121560
|
FINISHED |
| Object | imprint for innovative releases |
—
|
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: imprint for innovative releases | Statement: [Double Six Records, hasBrandRole, imprint for innovative releases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBrandRole Context triple: [Double Six Records, hasBrandRole, imprint for innovative releases]
-
A.
hasBrandType
Indicates that an entity is associated with or categorized under a particular brand type or classification.
-
B.
hasBrandName
Indicates that an entity is associated with or identified by a specific brand name.
-
C.
hasBrandConcept
Indicates that an entity is associated with or embodies a particular brand concept or branding idea.
-
D.
hasBrandIdentityElement
Indicates that an entity includes or is associated with a specific component of its overall brand identity (such as a logo, color scheme, or tagline).
-
E.
hasCoBrand
Indicates that two brands are jointly associated or partnered in offering a product, service, or marketing initiative.
- F. None of above. chosen
Provenance (4 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_69d87f1bb0988190b490d273dbf3fd03 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2020198908190b56900cbfc53f25c |
completed | April 17, 2026, 9:48 a.m. |
| PD | Predicate disambiguation | batch_69e1828518c48190a8ef3aaa46a1f639 |
completed | April 17, 2026, 12:44 a.m. |
| PDg | Predicate description generation | batch_69e183b9d3f08190953ada68f4272996 |
completed | April 17, 2026, 12:50 a.m. |
Created at: April 10, 2026, 5 a.m.