Triple
T7390027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Origin of German Tragic Drama |
E170474
|
entity |
| Predicate | periodAnalyzed |
P58040
|
FINISHED |
| Object | German Baroque |
—
|
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: German Baroque | Statement: [The Origin of German Tragic Drama, periodAnalyzed, German Baroque]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: periodAnalyzed Context triple: [The Origin of German Tragic Drama, periodAnalyzed, German Baroque]
-
A.
timePeriodAnalyzed
chosen
Indicates that a specified time period is the focus or scope of an analysis or evaluation.
-
B.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
C.
timePeriodCategory
Indicates the classification of a time period into a specific category or type (e.g., era, phase, or temporal grouping).
-
D.
periodizedAs
Indicates that something has been divided or organized into distinct time periods according to a particular periodization scheme.
-
E.
periodProperty
Indicates a temporal characteristic or attribute associated with a specific time period or interval.
- 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_69c68a5e2c9081909e713ce866e0060a |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2216a5c8190a933b24fda4530d8 |
completed | March 27, 2026, 9:09 p.m. |
| PD | Predicate disambiguation | batch_69c6f0309cc88190b55d278969400294 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:09 p.m.