Triple
T15095675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ejlert Løvborg |
E360529
|
entity |
| Predicate | isDestroyedBy |
P5325
|
FINISHED |
| Object | Hedda Gabler (burning his manuscript) |
—
|
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: Hedda Gabler (burning his manuscript) | Statement: [Ejlert Løvborg, isDestroyedBy, Hedda Gabler (burning his manuscript)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDestroyedBy Context triple: [Ejlert Løvborg, isDestroyedBy, Hedda Gabler (burning his manuscript)]
-
A.
destroyedFor
Indicates that one entity was ruined, eliminated, or rendered unusable specifically for the benefit, purpose, or objective of another entity.
-
B.
destroyedDuring
Indicates that one entity was destroyed in the course of, or as a consequence of, a specified event or time period.
-
C.
hasCauseOfDestruction
chosen
Indicates that one entity is the cause or agent responsible for the destruction or damage of another entity.
-
D.
destructionStatus
Indicates the condition or extent to which something has been damaged, ruined, or rendered unusable.
-
E.
typeOfDestruction
Indicates the specific manner or method by which something is destroyed or caused to cease to exist.
- 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_69d85a035aa88190b52a139d3a1b7b6d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005466e9c8190a68e1fbeb8922b1a |
completed | April 15, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69deb9645b9c8190a5712456dbd78029 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:04 a.m.