Triple
T16941444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burning of Cork |
E410957
|
entity |
| Predicate | estimatedBuildingsDestroyed |
P1583
|
FINISHED |
| Object | more than 300 buildings |
—
|
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: more than 300 buildings | Statement: [Burning of Cork, estimatedBuildingsDestroyed, more than 300 buildings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedBuildingsDestroyed Context triple: [Burning of Cork, estimatedBuildingsDestroyed, more than 300 buildings]
-
A.
buildingsDestroyed
chosen
Indicates that one or more buildings have been damaged to the point of destruction as a result of some event or action.
-
B.
numberOfBusinessesDestroyed
Indicates the quantity of businesses that have been destroyed in a given event or context.
-
C.
numberOfDistrictsDestroyed
Indicates the quantity of districts that have been destroyed in a given context or event.
-
D.
areaDestroyed
Indicates that a specified portion or region has been damaged or ruined to the point of destruction.
-
E.
mostStructuresDemolished
Indicates that the subject is the entity responsible for demolishing the greatest number of structures within a given context or set.
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cfadec70819095ec0048ebc71016 |
completed | April 18, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.