Triple
T12895452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prelude in D minor, BWV 851 |
E308479
|
entity |
| Predicate | hasCompanionPieceType |
P107324
|
FINISHED |
| Object | fugue |
—
|
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: fugue | Statement: [Prelude in D minor, BWV 851, hasCompanionPieceType, fugue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompanionPieceType Context triple: [Prelude in D minor, BWV 851, hasCompanionPieceType, fugue]
-
A.
hasCompanionPiece
Indicates that one item is conceptually or functionally paired with another item as its companion piece.
-
B.
usesPieceType
Indicates that one entity employs or operates using a specific type or category of piece as part of its function or activity.
-
C.
hasCompanionCandidate
Indicates that an entity is associated with another entity that is being considered or proposed as a potential companion.
-
D.
hasCompanionPillar
Indicates that an entity is associated with or supported by a corresponding companion pillar.
-
E.
notableCompanionType
Indicates that one entity is a prominent or significant type of companion or associate in relation to 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9717d859481908957510babac2d69 |
completed | April 10, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69d96fa776648190b9b5c30722ea50b6 |
completed | April 10, 2026, 9:46 p.m. |
| PDg | Predicate description generation | batch_69d9713e45a88190acd346f066093550 |
completed | April 10, 2026, 9:53 p.m. |
Created at: April 9, 2026, 5:40 p.m.