Triple
T29219131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moraz–Bruford |
E740761
|
entity |
| Predicate | notableInstrumentUsed |
P9123
|
FINISHED |
| Object | acoustic piano |
—
|
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: acoustic piano | Statement: [Moraz–Bruford, notableInstrumentUsed, acoustic piano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableInstrumentUsed Context triple: [Moraz–Bruford, notableInstrumentUsed, acoustic piano]
-
A.
notableInstrument
chosen
Indicates that an entity is especially known for playing or being associated with a particular musical instrument.
-
B.
instrumentsUsedBy
Indicates that a particular instrument, tool, or device is employed or utilized by a given entity to perform an action or achieve a result.
-
C.
notableInstrumentFeature
Indicates that an instrument is distinguished by a particular characteristic, quality, or component that is especially noteworthy or defining.
-
D.
usedAsInstrumentBy
Indicates that one entity functions as a tool, means, or instrument through which another entity performs an action or achieves an effect.
-
E.
notableInstrumentBuilt
Indicates that an entity is notable for having built or constructed a particular instrument.
- 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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_6a0326d40cb88190802f61fa832f8ca8 |
completed | May 12, 2026, 1:10 p.m. |
| PD | Predicate disambiguation | batch_6a03268b4f9c8190b3e135b37ed373c3 |
completed | May 12, 2026, 1:09 p.m. |
Created at: April 28, 2026, 12:14 p.m.