Triple
T37360058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inventions and Sinfonias |
E927552
|
entity |
| Predicate | hasThreePartSection |
P108499
|
FINISHED |
| Object | Sinfonias BWV 787–801 |
—
|
NE NERFINISHED |
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: Sinfonias BWV 787–801 | Statement: [Inventions and Sinfonias, hasThreePartSection, Sinfonias BWV 787–801]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasThreePartSection Context triple: [Inventions and Sinfonias, hasThreePartSection, Sinfonias BWV 787–801]
-
A.
hasThreePartStructure
chosen
Indicates that something is organized into three distinct, related parts or sections.
-
B.
hasSect
Indicates that an entity includes, contains, or is associated with a particular sect or subgroup within a larger religious, ideological, or organizational context.
-
C.
isMultiSectional
Indicates that something is composed of or divided into multiple distinct sections or parts.
-
D.
hasTwoPartStructure
Indicates that something is composed of exactly two distinct, structured parts that together form a whole.
-
E.
has2DSection
Indicates that one entity represents a two-dimensional cross-sectional view or slice of another entity.
- 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_69f76eb701788190b40824bc4594d985 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:16 p.m.