Triple
T12503192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pentheus |
E298880
|
entity |
| Predicate | roleInTheBacchae |
P9987
|
FINISHED |
| Object | king of Thebes |
—
|
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: king of Thebes | Statement: [Pentheus, roleInTheBacchae, king of Thebes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInTheBacchae Context triple: [Pentheus, roleInTheBacchae, king of Thebes]
-
A.
mythologicalRole
chosen
Indicates the specific function, duty, or status an entity holds within a mythological or legendary context.
-
B.
roleInTheology
Indicates the specific function, position, or significance an entity holds within a theological system, doctrine, or belief framework.
-
C.
theaterRole
Indicates that an entity holds or performs a specific role or character in a theatrical production in relation to another entity (such as a play or performance).
-
D.
dramaticStructureRole
Indicates the specific function or role an element plays within the overall dramatic structure of a narrative or performance.
-
E.
roleInRomeoAndJuliet
Indicates the specific character or part that an entity plays in the work "Romeo and Juliet."
- 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_69d6ada4cd388190ae3bbf83ff87057a |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94dfcea188190a929db1aabe1a286 |
completed | April 10, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69d94d43b7008190af2648fe09fd6d23 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:57 p.m.