Triple
T28913103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Timmy Trumpet |
E733282
|
entity |
| Predicate | usesInstrumentOnStage |
P39878
|
FINISHED |
| Object | trumpet |
—
|
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: trumpet | Statement: [Timmy Trumpet, usesInstrumentOnStage, trumpet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesInstrumentOnStage Context triple: [Timmy Trumpet, usesInstrumentOnStage, trumpet]
-
A.
usesInstrumentsOnStage
chosen
Indicates that an entity performs on stage while making use of musical instruments.
-
B.
usesInstrument
Indicates that an agent performs an action by employing a specific instrument or tool as the means to carry it out.
-
C.
usesStage
Indicates that one entity employs or operates on another entity at a particular phase or stage within a process or workflow.
-
D.
reliesOnInstrument
Indicates that an action or process depends on or is carried out using a particular instrument or tool.
-
E.
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.
- 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_69f05b096d208190958a57d2e4b5a93a |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 8:12 a.m.