Triple
T23310455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 2 in B-flat major |
E590567
|
entity |
| Predicate | openingSectionType |
P78700
|
FINISHED |
| Object | orchestral sinfonia |
—
|
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: orchestral sinfonia | Statement: [Symphony No. 2 in B-flat major, openingSectionType, orchestral sinfonia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingSectionType Context triple: [Symphony No. 2 in B-flat major, openingSectionType, orchestral sinfonia]
-
A.
openingSequenceType
chosen
Indicates the specific kind or category of an opening sequence associated with an entity or event.
-
B.
openedWithSection
Indicates that something (such as a document, file, or resource) is opened starting from or via a specific section.
-
C.
openedSectionBetween
Indicates that one entity has created or established an open section, gap, or interval between itself and another entity.
-
D.
openingStyle
Indicates how something is initially presented, introduced, or begun in terms of manner, format, or approach.
-
E.
openedInSection
Indicates that something was opened or initiated within a specific section or subsection of a larger structure or context.
- 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_69e25d1d32188190948eb76909d1dcc3 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1972acad08190bb56541b822555cd |
completed | April 29, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69effcf325f88190b320268c3c551abb |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 5:05 p.m.