Triple
T36547030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bardings |
E901164
|
entity |
| Predicate | sufferedDestructionOfCity |
P31453
|
FINISHED |
| Object | Sack of Dale |
—
|
NE NERFINISHED |
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: Sack of Dale | Statement: [Bardings, sufferedDestructionOfCity, Sack of Dale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sufferedDestructionOfCity Context triple: [Bardings, sufferedDestructionOfCity, Sack of Dale]
-
A.
destroyedCity
Indicates that an entity has caused the complete or near-complete destruction of a city.
-
B.
mainCityDestroyed
Indicates that the primary or central city associated with an entity has been destroyed.
-
C.
sufferedDestructionOf
Indicates that one entity experienced damage, ruin, or loss as a result of the destruction of another entity.
-
D.
sufferedDestructionIn
chosen
Indicates that an entity experienced damage, ruin, or devastation during or as part of a specified event or period.
-
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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.