Triple
T10138716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dyskolos |
E226924
|
entity |
| Predicate | hasModernPerformances |
P92481
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Dyskolos, hasModernPerformances, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModernPerformances Context triple: [Dyskolos, hasModernPerformances, yes]
-
A.
notableModernPerformancePractice
Indicates that the subject is recognized for a significant contemporary or historically informed way of performing a work, influencing how it is interpreted or executed in modern practice.
-
B.
hasModernAdaptations
Indicates that the subject work has been reinterpreted or recreated in contemporary forms, such as recent films, series, books, or other modern media adaptations.
-
C.
hasModernEditions
Indicates that an original work or text has one or more updated or contemporary published editions.
-
D.
hasLivePerformanceWith
Indicates that two or more entities participate together in the same live performance event.
-
E.
hasLivePerformanceStyle
Indicates that an entity is associated with a particular style or manner of live performance.
- 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_69ca8433ec308190b8b25a6fe359c34c |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cde88344a481909ee833451fab6e58 |
completed | April 2, 2026, 3:54 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba4f5d88190ba68e63be10b08c7 |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd51bc440c819086320900701f87c2 |
completed | April 1, 2026, 5:11 p.m. |
Created at: March 30, 2026, 9:06 p.m.