Triple
T32915068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ein bürgerliches Trauerspiel |
E841984
|
entity |
| Predicate | marksWorkAs |
P175388
|
FINISHED |
| Object | tragedy |
—
|
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: tragedy | Statement: [Ein bürgerliches Trauerspiel, marksWorkAs, tragedy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marksWorkAs Context triple: [Ein bürgerliches Trauerspiel, marksWorkAs, tragedy]
-
A.
marksStatus
Indicates that one entity assigns, records, or updates the status or condition of another entity.
-
B.
marksOn
Indicates that one entity bears visible signs, traces, or imprints that have been made or left by another entity.
-
C.
namedForWorkOn
Indicates that an entity is named in honor of another entity specifically because of that entity’s work or contributions in a particular field or endeavor.
-
D.
coordinatesWorkOf
Indicates overseeing and organizing the tasks, efforts, or activities of others to ensure they work together effectively toward a common goal.
-
E.
namedForWork
Indicates that one entity is named in honor of, or derived from the title of, a particular work (such as a book, film, artwork, or other creative production).
- 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_69f3494779388190a5d3e97f92278be2 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d1d916f881909575c2b22c416a5b |
completed | May 3, 2026, 4:40 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
| PDg | Predicate description generation | batch_69f6d0d331dc8190be5aa6bfc6365e67 |
completed | May 3, 2026, 4:36 a.m. |
Created at: May 1, 2026, 1:19 a.m.