Triple
T4724382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilbury Records |
E104844
|
entity |
| Predicate | labelBrandingUsedOn |
P11989
|
FINISHED |
| Object | Traveling Wilburys Vol. 1 packaging |
—
|
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: Traveling Wilburys Vol. 1 packaging | Statement: [Wilbury Records, labelBrandingUsedOn, Traveling Wilburys Vol. 1 packaging]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: labelBrandingUsedOn Context triple: [Wilbury Records, labelBrandingUsedOn, Traveling Wilburys Vol. 1 packaging]
-
A.
usedBrand
Indicates that an entity has utilized, applied, or operated a particular brand in some context.
-
B.
brandUsage
Indicates that one entity uses, features, or is associated with another entity’s brand in its products, services, or communications.
-
C.
hasBranding
chosen
Indicates that one entity carries, displays, or is associated with the brand identity of another entity.
-
D.
usedInBrand
Indicates that something (such as a component, material, or element) is utilized as part of or within a particular brand.
-
E.
logoUsedBy
Indicates that a particular logo is employed or displayed by a specific entity as part of its identity, branding, or representation.
- 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_69bd43ed84648190ae0b7ee8e8d00482 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd67c9c3c08190a6c4944cdd1362a8 |
completed | March 20, 2026, 3:29 p.m. |
| PD | Predicate disambiguation | batch_69bd6220071881909670c89d072ffb6d |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:18 p.m.