Triple
T13154487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prelude in E minor, BWV 855 |
E312547
|
entity |
| Predicate | keyOrderInBookI |
P37518
|
FINISHED |
| Object | E minor prelude |
—
|
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: E minor prelude | Statement: [Prelude in E minor, BWV 855, keyOrderInBookI, E minor prelude]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyOrderInBookI Context triple: [Prelude in E minor, BWV 855, keyOrderInBookI, E minor prelude]
-
A.
book1Contains
Indicates that one book includes, encloses, or has as part of its content another specified element or section.
-
B.
appearsInBookNumber
Indicates that an entity is featured or mentioned in a specific book identified by its number within a series or collection.
-
C.
book5Content
Indicates that one entity is the content or textual material contained within the book represented by the other entity.
-
D.
orderOf
chosen
Indicates that one entity is arranged, ranked, or sequenced before or after another according to a specified ordering criterion.
-
E.
orderInKojiki
Indicates the relative sequence or position of something as it appears within the text of the Kojiki.
- 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_69d806aabde48190899e13e41659cae5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bbd1d088190b7c69f37fc6eeb64 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:11 p.m.