Triple
T37813537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Street Glide |
E942711
|
entity |
| Predicate | hasInfotainmentBrand |
P125215
|
FINISHED |
| Object | Harley-Davidson Boom! Box |
—
|
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: Harley-Davidson Boom! Box | Statement: [Street Glide, hasInfotainmentBrand, Harley-Davidson Boom! Box]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInfotainmentBrand Context triple: [Street Glide, hasInfotainmentBrand, Harley-Davidson Boom! Box]
-
A.
hasEntertainmentBrand
Indicates that one entity owns, operates, or is formally associated with an entertainment-related brand or franchise.
-
B.
containsComponentBrand
chosen
Indicates that an entity includes, as part of its composition or structure, a component produced or branded by a specified brand.
-
C.
hasBrandType
Indicates that an entity is associated with or categorized under a particular brand type or classification.
-
D.
hasBrandName
Indicates that an entity is associated with or identified by a specific brand name.
-
E.
hasBrandConcept
Indicates that an entity is associated with or embodies a particular brand concept or branding idea.
- 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_69f76ee8104c8190ab17133ccd8f86e6 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a0136e4af808190b529d324bbf0c5d9 |
completed | May 11, 2026, 1:54 a.m. |
| PD | Predicate disambiguation | batch_6a01369141c4819091cb8064913a44ca |
completed | May 11, 2026, 1:53 a.m. |
Created at: May 3, 2026, 4:19 p.m.