Triple
T3241644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christiansborg Palace |
E67976
|
entity |
| Predicate | secondPalaceDestroyedIn |
P31453
|
FINISHED |
| Object | 1884 |
—
|
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: 1884 | Statement: [Christiansborg Palace, secondPalaceDestroyedIn, 1884]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondPalaceDestroyedIn Context triple: [Christiansborg Palace, secondPalaceDestroyedIn, 1884]
-
A.
sufferedDestructionIn
chosen
Indicates that an entity experienced damage, ruin, or devastation during or as part of a specified event or period.
-
B.
mainCityDestroyed
Indicates that the primary or central city associated with an entity has been destroyed.
-
C.
destroyedCity
Indicates that an entity has caused the complete or near-complete destruction of a city.
-
D.
rebuiltAsPalace
Indicates that a structure or building was reconstructed or transformed into a palace.
-
E.
citySacked
Indicates that a city has been violently attacked, looted, and destroyed or heavily damaged, typically as a result of military conquest.
- 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_69ad858d27348190abb61c280b4c86a9 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaef76d908190815bb456e366ee0a |
completed | March 8, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69ada4159e0481908cbbdd750f5e08c7 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:08 p.m.