Triple
T11475046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D minor (BWV 1004) |
E272004
|
entity |
| Predicate | parallelMajor |
P99487
|
FINISHED |
| Object | D major |
—
|
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: D major | Statement: [D minor (BWV 1004), parallelMajor, D major]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parallelMajor Context triple: [D minor (BWV 1004), parallelMajor, D major]
-
A.
parallel
Indicates that two or more entities maintain a constant separation and direction without intersecting or converging.
-
B.
parallelPassage
Indicates that one text segment corresponds closely in content or structure to another, such that they can be considered parallel versions or accounts of the same material.
-
C.
parallelSubdivision
Indicates that one structure or process is divided into multiple parts that proceed or are handled simultaneously alongside each other.
-
D.
parallelPosition
Indicates that two entities occupy positions that are aligned in parallel relative to a reference frame or axis.
-
E.
isMajorFastAlongWith
Indicates that an entity is a primary or significant fast-moving element occurring together or in coordination with another entity.
- 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_69d6aae0c8d881908a5a360c0be3242e |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8294c8dc48190a515f83c99405a3b |
completed | April 9, 2026, 10:33 p.m. |
| PD | Predicate disambiguation | batch_69d8086ecd6c81908f424864857762d6 |
completed | April 9, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69d8279925e4819089210611c0d8e61a |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 8, 2026, 9:36 p.m.