Triple
T23218556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurpfalz |
E580817
|
entity |
| Predicate | HeidelbergCastleDestroyedIn |
P31453
|
FINISHED |
| Object | late 17th century |
—
|
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: late 17th century | Statement: [Kurpfalz, HeidelbergCastleDestroyedIn, late 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HeidelbergCastleDestroyedIn Context triple: [Kurpfalz, HeidelbergCastleDestroyedIn, late 17th century]
-
A.
fortressDemolishedIn
Indicates that a fortress was demolished or destroyed during a specified time or event.
-
B.
palaceDemolished
Indicates that a palace has been destroyed or torn down, typically as a completed event.
-
C.
originalChurchDestroyed
Indicates that the initially established church building was demolished or ceased to exist, typically due to destruction rather than relocation or replacement.
-
D.
sufferedDestructionIn
chosen
Indicates that an entity experienced damage, ruin, or devastation during or as part of a specified event or period.
-
E.
firstPalaceDestroyedBy
Indicates that the subject’s first palace was destroyed by the specified agent or cause.
- 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_69e2460389408190be74f41d217799a9 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f191675de48190858907872a065c56 |
completed | April 29, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69effcccee508190a7ae311fdd319806 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:08 p.m.