Triple
T8908429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portsmouth Point Overture |
E212119
|
entity |
| Predicate | intendedEnsembleType |
P25465
|
FINISHED |
| Object | symphony orchestra |
—
|
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: symphony orchestra | Statement: [Portsmouth Point Overture, intendedEnsembleType, symphony orchestra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedEnsembleType Context triple: [Portsmouth Point Overture, intendedEnsembleType, symphony orchestra]
-
A.
intendedEnsemble
Indicates that one entity is designed, chosen, or specified to function as the ensemble or group counterpart associated with another entity.
-
B.
typeOfEnsemble
Indicates the specific kind or category of ensemble that an entity belongs to or represents.
-
C.
typicalEnsembleType
chosen
Indicates the usual or characteristic type of ensemble associated with or used to perform a given work, piece, or musical context.
-
D.
isPartOfEnsemble
Indicates that an entity belongs to, or is a member of, a larger group or ensemble.
-
E.
musicalTexture
Indicates the type of overall sonic fabric or layering in a piece of music, such as how melodic, harmonic, and rhythmic elements are combined or interwoven.
- 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_69ca839255248190b43984294abd92ae |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc65207bbc8190be181555b9564797 |
completed | April 1, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69cc5ecf55248190a29f00fbf99f13c4 |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:55 p.m.