Triple
T20474586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prez |
E502277
|
entity |
| Predicate | appliedToInstrument |
P129090
|
FINISHED |
| Object | tenor saxophone |
—
|
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: tenor saxophone | Statement: [Prez, appliedToInstrument, tenor saxophone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedToInstrument Context triple: [Prez, appliedToInstrument, tenor saxophone]
-
A.
appliesInstrument
chosen
Indicates that an agent performs an action using a specific instrument or tool as the means to carry out that action.
-
B.
alsoAppliesInstrument
Indicates that a condition, rule, or characteristic that applies to one instrument also applies to another instrument.
-
C.
usesInstrument
Indicates that an agent performs an action by employing a specific instrument or tool as the means to carry it out.
-
D.
allowedInstrument
Indicates that a particular instrument is permitted or authorized for use in a given context or activity.
-
E.
relatesToInstrument
Indicates a relationship where one entity is associated with, involves, or makes use of a particular instrument or tool.
- 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_69e0b4ae5f1081908768b0c9a3a0bf38 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e699639eec81908f8bd24877b2b876 |
completed | April 20, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69e5768372988190b08ef8ae67d42ab6 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:33 a.m.