Triple
T19895753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hammond organ |
E478147
|
entity |
| Predicate | hasTypicalAccessory |
P31021
|
FINISHED |
| Object | Leslie speaker |
—
|
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: Leslie speaker | Statement: [Hammond organ, hasTypicalAccessory, Leslie speaker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalAccessory Context triple: [Hammond organ, hasTypicalAccessory, Leslie speaker]
-
A.
hasAccessoryType
Indicates that an entity is associated with or characterized by a particular type or category of accessory.
-
B.
accessory
chosen
Indicates that one entity serves as a supplementary or supporting item to another, often enhancing its function, use, or appearance.
-
C.
hasAccessoryEcosystem
Indicates that an entity is associated with a surrounding set of compatible accessories, add-ons, or peripheral products designed to work with it.
-
D.
hasTypicalAccess
Indicates that one entity normally or customarily has the ability, permission, or means to access or use another entity.
-
E.
typicallyHolds
Indicates that a certain relationship or condition generally holds true in typical or normal situations, though not necessarily in all cases.
- 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.