Triple
T5431939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alcestis |
E121513
|
entity |
| Predicate | choralMeter |
P63720
|
FINISHED |
| Object | various lyric meters in choral odes |
—
|
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: various lyric meters in choral odes | Statement: [Alcestis, choralMeter, various lyric meters in choral odes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: choralMeter Context triple: [Alcestis, choralMeter, various lyric meters in choral odes]
-
A.
notableChorale
Indicates that a subject is recognized for or associated with a significant or distinguished chorale work or composition.
-
B.
chorus
Indicates that multiple entities jointly produce or participate in a coordinated vocal or expressive performance, typically as a unified group.
-
C.
chorusDirector
Indicates that one entity serves as the director or leader of a chorus in relation to another entity.
-
D.
hasChorus
Indicates that something (typically a song or musical piece) includes a chorus section as part of its structure.
-
E.
commonlySungStanzas
Indicates that certain stanzas of a song or poem are those most frequently sung or performed in practice.
- 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_69bd463c65f0819082ee6483ab4b466a |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8911a7348190ad9378a248190f07 |
completed | March 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69bd846b8bdc81909dcdc2a3084226f2 |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd8910de688190aa0cd80627849a60 |
completed | March 20, 2026, 5:51 p.m. |
Created at: March 20, 2026, 2:06 p.m.