Triple
T19970466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thesmophoriazusae |
E480057
|
entity |
| Predicate | parodiesSpecificWork |
P10352
|
FINISHED |
| Object | Euripides’ plays and tragic style in general |
—
|
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: Euripides’ plays and tragic style in general | Statement: [Thesmophoriazusae, parodiesSpecificWork, Euripides’ plays and tragic style in general]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parodiesSpecificWork Context triple: [Thesmophoriazusae, parodiesSpecificWork, Euripides’ plays and tragic style in general]
-
A.
parodies
chosen
Indicates that one entity imitates another in an exaggerated or humorous way, often to criticize or comment on the original.
-
B.
isHumorousWork
Indicates that a work is intended to be humorous or comedic in nature.
-
C.
hasHumorousTreatmentOf
Indicates that one entity presents or portrays another entity in a humorous, comedic, or joking manner.
-
D.
adaptedWorkOf
Indicates that one work is derived from, based on, or reinterprets the content of another pre-existing work.
-
E.
adaptedWorkOfAuthor
Indicates that a work is an adaptation derived from, based on, or reinterpreting the original work of a specified author.
- 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65bc89b508190879d29bef546aac8 |
completed | April 20, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69e537f7e4848190b431a69ec3f1b609 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.