Triple
T26065317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matthias Jabs |
E657382
|
entity |
| Predicate | hasInstrumentBrandEndorsement |
P91438
|
FINISHED |
| Object | Fender Stratocaster |
—
|
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: Fender Stratocaster | Statement: [Matthias Jabs, hasInstrumentBrandEndorsement, Fender Stratocaster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInstrumentBrandEndorsement Context triple: [Matthias Jabs, hasInstrumentBrandEndorsement, Fender Stratocaster]
-
A.
hasBrandRole
Indicates that an entity holds a specific functional or organizational role in relation to a particular brand.
-
B.
hasInstrumentRole
Indicates that an entity participates in an action or process specifically in the capacity of an instrument or means by which that action is carried out.
-
C.
hasBrandType
Indicates that an entity is associated with or categorized under a particular brand type or classification.
-
D.
supportsBrand
chosen
Indicates that one entity endorses, promotes, or is compatible with a particular brand.
-
E.
hasTerminalBrand
Indicates that an entity is associated with, or operates under, a specific terminal 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_69ee5bbd788481909e22bd7153d0c037 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: April 26, 2026, 7:23 p.m.