Triple
T37360057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inventions and Sinfonias |
E927552
|
entity |
| Predicate | hasTwoPartSection |
P48977
|
FINISHED |
| Object | Inventions BWV 772–786 |
—
|
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: Inventions BWV 772–786 | Statement: [Inventions and Sinfonias, hasTwoPartSection, Inventions BWV 772–786]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTwoPartSection Context triple: [Inventions and Sinfonias, hasTwoPartSection, Inventions BWV 772–786]
-
A.
hasTwoPartStructure
chosen
Indicates that something is composed of exactly two distinct, structured parts that together form a whole.
-
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.
hasSectionOn
Indicates that one entity (typically a document or resource) contains a dedicated section or part that specifically addresses or discusses another entity or topic.
-
E.
hasSeparatedSections
Indicates that something is divided into distinct, non-continuous parts or sections.
- 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_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:16 p.m.