Triple
T17940929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castle of Eger |
E448583
|
entity |
| Predicate | destroyedPartiallyIn |
P11808
|
FINISHED |
| Object | 18th 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: 18th century | Statement: [Castle of Eger, destroyedPartiallyIn, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: destroyedPartiallyIn Context triple: [Castle of Eger, destroyedPartiallyIn, 18th century]
-
A.
partiallyDestroyed
Indicates that an entity has been damaged or ruined to a significant extent but not completely destroyed.
-
B.
partlyDismantledBy
Indicates that an entity has been only partially taken apart, removed, or deconstructed by another agent or process.
-
C.
restoredInPart
Indicates that something has been brought back to a previous or improved state, but only partially rather than fully.
-
D.
destroyedDuring
chosen
Indicates that one entity was destroyed in the course of, or as a consequence of, a specified event or time period.
-
E.
partiallyRestored
Indicates that an entity has been brought back toward a previous or original state, but the restoration is incomplete or only partially achieved.
- 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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4ad95f4608190b1ebb45944218f07 |
completed | April 19, 2026, 10:25 a.m. |
| PD | Predicate disambiguation | batch_69e3f8e713d481908b4a126258c18b63 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:21 a.m.