Triple
T11434517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toccata |
E270970
|
entity |
| Predicate | typicallyWrittenFor |
P1996
|
FINISHED |
| Object | keyboard instruments |
—
|
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: keyboard instruments | Statement: [Toccata, typicallyWrittenFor, keyboard instruments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyWrittenFor Context triple: [Toccata, typicallyWrittenFor, keyboard instruments]
-
A.
originallyWrittenFor
chosen
Indicates that a work was initially created or composed with a particular recipient, medium, context, or purpose in mind.
-
B.
writesForAudience
Indicates that an agent creates written content intended specifically for a particular audience or readership.
-
C.
writtenIn
Indicates that a work (such as a text, program, or document) is expressed or encoded using a particular language or notation.
-
D.
currentlyWrittenIn
Indicates that a work or document is, at the present time, expressed or composed in a particular language or writing system.
-
E.
areWrittenOn
Indicates that one entity serves as a surface or medium on which another entity is inscribed, recorded, or written.
- 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_69d6aadeef688190874bcecd88b3dd9b |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d806c485f481909dd3d9b0993f3faf |
completed | April 9, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69d7e71436f88190ac7e45a04ea5c987 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:35 p.m.