Triple
T21058950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chorus of citizens of Pherae |
E518800
|
entity |
| Predicate | functionInDrama |
P20800
|
FINISHED |
| Object | commentary on action |
—
|
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: commentary on action | Statement: [Chorus of citizens of Pherae, functionInDrama, commentary on action]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionInDrama Context triple: [Chorus of citizens of Pherae, functionInDrama, commentary on action]
-
A.
dramaticFunction
chosen
Indicates the role or purpose that something serves within the structure or progression of a dramatic work or narrative.
-
B.
filmicFunction
Indicates the role or purpose that something serves within the structure, style, or narrative function of a film.
-
C.
theatricalFunction
Indicates the role or purpose something serves within a theatrical context, such as its function in staging, performance, or dramatic presentation.
-
D.
dramaType
Indicates the specific category or genre of drama that characterizes an entity or work.
-
E.
dramaticAction
Indicates an action or event characterized by heightened emotion, tension, or significance that drives or intensifies a dramatic situation or narrative.
- 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_69e0b5053ac48190921529544959e906 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fd8236b481908eebfaeeb2aa63e6 |
completed | April 21, 2026, 4:30 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf9d71881908cd85dfc37db93ca |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:37 p.m.