Triple
T24047216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Casimir |
E595555
|
entity |
| Predicate | demolishedOrObsolete |
P154661
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Fort Casimir, demolishedOrObsolete, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demolishedOrObsolete Context triple: [Fort Casimir, demolishedOrObsolete, yes]
-
A.
demolishedOrDestroyed
Indicates that one entity has caused another entity to be torn down, ruined, or rendered unusable, typically through deliberate demolition or destructive force.
-
B.
demolishedWith
Indicates that one entity was destroyed or torn down using another specified tool, method, or agent.
-
C.
demolishedAfter
Indicates that one entity was demolished at a point in time later than the demolition of another entity.
-
D.
demolished
Indicates that one entity completely destroyed or razed another entity, typically a structure or object, so that it no longer exists in its previous form.
-
E.
demolishedUnder
Indicates that one entity was demolished or destroyed as a result of the authority, order, or conditions imposed by another entity.
- F. None of above. chosen
Provenance (4 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_69e288c06a908190899cad4531f32c9a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d9cd50648190b009e97e5be53e8b |
completed | April 29, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f1764345388190a3102b62ddb729b4 |
completed | April 29, 2026, 3:08 a.m. |
| PDg | Predicate description generation | batch_69f1785afe3c81909be28986ffe944bf |
completed | April 29, 2026, 3:17 a.m. |
Created at: April 17, 2026, 10:17 p.m.