Triple
T8522909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corinna |
E201735
|
entity |
| Predicate | metricalPractice |
P46136
|
FINISHED |
| Object | Aeolic meters |
—
|
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: Aeolic meters | Statement: [Corinna, metricalPractice, Aeolic meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metricalPractice Context triple: [Corinna, metricalPractice, Aeolic meters]
-
A.
musicPractice
Indicates engaging in the activity of practicing or rehearsing music, typically to improve skill or prepare for performance.
-
B.
metricalFeature
chosen
Indicates a relationship where one entity specifies or characterizes a metrical property or pattern of another entity.
-
C.
rhythmicOrganization
Indicates how temporal patterns, accents, and durations are structured or arranged in relation to one another within a sequence or system.
-
D.
musicTheoryContext
Indicates that one entity is interpreted or analyzed within the framework, rules, or concepts of music theory in relation to another entity or situation.
-
E.
choralMeter
Indicates a relationship where a musical work or passage is characterized by a specific metrical pattern typical of choral music.
- 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_69ca8321bb44819081b74df0b710276d |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe64215408190b45f462a32d3471d |
completed | March 31, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69cbd10f64b4819080859057c19e58f0 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:16 p.m.