Triple
T4008221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Summer Palace |
E89577
|
entity |
| Predicate | perpetratorOfDestruction |
P698
|
FINISHED |
| Object | British troops |
—
|
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: British troops | Statement: [Old Summer Palace, perpetratorOfDestruction, British troops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perpetratorOfDestruction Context triple: [Old Summer Palace, perpetratorOfDestruction, British troops]
-
A.
typeOfDestruction
Indicates the specific manner or method by which something is destroyed or caused to cease to exist.
-
B.
designedToDestroy
Indicates that one entity was intentionally created or configured for the purpose of damaging, disabling, or annihilating another entity.
-
C.
perpetratedBy
chosen
Indicates that an action, event, or wrongdoing was carried out or caused by a particular agent or entity.
-
D.
commanderOfPerpetrators
Indicates that one entity holds command authority over the individuals who carried out a particular act or offense.
-
E.
perpetratorAllegiance
Indicates that the perpetrator is affiliated with, loyal to, or acting on behalf of a particular group, organization, 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_69aed9585e788190bec2d39deba3750f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaec08dc8190a341809059554f84 |
completed | March 9, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69aef8fa6fec81909b1190ecbba61410 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:34 p.m.