Triple
T8404910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Domenico Montagnana |
E198469
|
entity |
| Predicate | instrumentRarity |
P81823
|
FINISHED |
| Object | original instruments are rare |
—
|
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: original instruments are rare | Statement: [Domenico Montagnana, instrumentRarity, original instruments are rare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: instrumentRarity Context triple: [Domenico Montagnana, instrumentRarity, original instruments are rare]
-
A.
musicInstrumentation
Indicates the specific instruments or instrumental forces used to perform a piece of music.
-
B.
numberInInstrument
Indicates that an entity specifies the count or quantity of items contained within or associated with a particular instrument.
-
C.
reliesOnInstrument
Indicates that an action or process depends on or is carried out using a particular instrument or tool.
-
D.
notableInstrument
Indicates that an entity is especially known for playing or being associated with a particular musical instrument.
-
E.
instrumentalIn
Indicates that one entity serves as a crucial means, tool, or contributing factor in bringing about an outcome or enabling another entity’s action or effect.
- F. None of above. chosen
Provenance (4 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_69ca8310df9c8190b25f16161cca3e41 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb83116bf48190894bd5d5465520ef |
completed | March 31, 2026, 8:17 a.m. |
| PD | Predicate disambiguation | batch_69cb70d473dc8190af8ea81ee5aa970d |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76da264881909483b835e1db06da |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 6:05 p.m.