Triple
T19895786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hammond organ |
E478147
|
entity |
| Predicate | isAssociatedWithBrand |
P133890
|
FINISHED |
| Object | Hammond Suzuki |
—
|
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: Hammond Suzuki | Statement: [Hammond organ, isAssociatedWithBrand, Hammond Suzuki]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAssociatedWithBrand Context triple: [Hammond organ, isAssociatedWithBrand, Hammond Suzuki]
-
A.
isBrand
chosen
Indicates that one entity functions as the commercial brand or label associated with another entity.
-
B.
componentTypeAssociatedWithBrand
Indicates that a specific component type is linked or affiliated with a particular brand.
-
C.
brandAssociationType
Indicates the specific nature of the relationship or association that exists between a brand and another entity (such as a product, organization, or campaign).
-
D.
usedBrandOf
Indicates that one entity made use of or operated an item, product, or service associated with a particular brand.
-
E.
hasBrandRole
Indicates that an entity holds a specific functional or organizational role in relation to a particular brand.
- 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_69d8e520682081909892916424699bd5 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6593cb45881909cc34a9c601db001 |
completed | April 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69e537ecda248190895c96afb6243823 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:52 p.m.