Triple
T12793076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony |
E305816
|
entity |
| Predicate | hasTypicalStructure |
P841
|
FINISHED |
| Object | Multi-movement work |
—
|
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: Multi-movement work | Statement: [Symphony, hasTypicalStructure, Multi-movement work]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalStructure Context triple: [Symphony, hasTypicalStructure, Multi-movement work]
-
A.
hasStructureType
chosen
Indicates that an entity possesses or is classified by a specific structural type or configuration.
-
B.
hasHumanStructure
Indicates that one entity possesses or exhibits a structural form or organization characteristic of humans.
-
C.
hasSignificantStructure
Indicates that an entity possesses a structure or internal organization that is notably complex, important, or meaningful in a given context.
-
D.
hasRealStructure
Indicates that an abstract object or system is endowed with a concrete, well-defined mathematical or physical structure that makes it realizable or interpretable in a real-world or formal model.
-
E.
hasStructureCode
Indicates that an entity is associated with a specific structural identifier or code that defines its organization or configuration.
- 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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e6ca0288190aba01735b71a01da |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d9640ba0688190973e4e7ec8d4a8e0 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:30 p.m.