Triple
T11019049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nocturnes |
E260437
|
entity |
| Predicate | thirdMovementAdditionalForces |
P96594
|
FINISHED |
| Object | women's chorus |
—
|
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: women's chorus | Statement: [Nocturnes, thirdMovementAdditionalForces, women's chorus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thirdMovementAdditionalForces Context triple: [Nocturnes, thirdMovementAdditionalForces, women's chorus]
-
A.
thirdMovementType
Indicates the specific type or category of the third movement within a larger sequence or structure of movements.
-
B.
componentForces
Indicates that a force is decomposed into its constituent directional components that together produce the original overall force.
-
C.
axisForces
Indicates a relationship where one entity exerts or applies force along, around, or with respect to a particular axis defined by another entity.
-
D.
thirdMovementKey
Indicates the musical key in which the third movement of a multi-movement work is composed or performed.
-
E.
axisForcesStrength
Indicates the magnitude or intensity of forces acting along a specified axis.
- F. None of above. chosen
Provenance (4 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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797a9e8788190a0f45b52bad1bfb5 |
completed | April 9, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69d72e995e008190bbffb314129ed0cd |
completed | April 9, 2026, 4:44 a.m. |
| PDg | Predicate description generation | batch_69d732242fdc8190be77d1f730a42935 |
completed | April 9, 2026, 4:59 a.m. |
Created at: April 8, 2026, 9:25 p.m.