Triple
T32115956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monster Cable Products |
E820237
|
entity |
| Predicate | hasBrandPerception |
P73564
|
FINISHED |
| Object | high-end |
—
|
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: high-end | Statement: [Monster Cable Products, hasBrandPerception, high-end]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBrandPerception Context triple: [Monster Cable Products, hasBrandPerception, high-end]
-
A.
hasBrandImpact
Indicates that one entity affects, influences, or contributes to the perception, value, or performance of a brand associated with another entity.
-
B.
hasBrandReputation
chosen
Indicates that an entity possesses a certain level or type of perceived quality, trustworthiness, or public image associated with its brand.
-
C.
hasBrandRecognitionFor
Indicates that one entity is aware of, recognizes, or can identify the brand of another entity.
-
D.
hasBrandConcept
Indicates that an entity is associated with or embodies a particular brand concept or branding idea.
-
E.
usesBrandReputationOf
Indicates that one entity leverages or capitalizes on the brand reputation of another entity for its own purposes.
- 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: May 1, 2026, 12:28 a.m.