Triple
T33049761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hiketides |
E845690
|
entity |
| Predicate | chorusRole |
P175744
|
FINISHED |
| Object | Danaids as collective protagonist |
—
|
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: Danaids as collective protagonist | Statement: [Hiketides, chorusRole, Danaids as collective protagonist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chorusRole Context triple: [Hiketides, chorusRole, Danaids as collective protagonist]
-
A.
chorus
Indicates that multiple entities jointly produce or participate in a coordinated vocal or expressive performance, typically as a unified group.
-
B.
chorusType
Indicates the specific kind or category of chorus associated with an entity (e.g., type of vocal ensemble or choral grouping).
-
C.
chorusFeature
Indicates that one entity participates in or is highlighted within the chorus section of another entity, such as a song or musical piece.
-
D.
chorusDirector
Indicates that one entity serves as the director or leader of a chorus in relation to another entity.
-
E.
chorusPerformer
Indicates that an entity performs as a member of the chorus in a musical or theatrical work.
- 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d6a482fc8190b526291cd99b8696 |
completed | May 3, 2026, 5:01 a.m. |
Created at: May 1, 2026, 1:24 a.m.