Triple
T24024729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aldersgate Street, London |
E594919
|
entity |
| Predicate | historicallyDamagedBy |
P993
|
FINISHED |
| Object | The Blitz |
—
|
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: The Blitz | Statement: [Aldersgate Street, London, historicallyDamagedBy, The Blitz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyDamagedBy Context triple: [Aldersgate Street, London, historicallyDamagedBy, The Blitz]
-
A.
disasterHistory
Indicates that there is a record of past disasters or catastrophic events associated with the entity.
-
B.
damagedBy
chosen
Indicates that one entity has caused harm, impairment, or deterioration to another entity.
-
C.
historicallyProneTo
Indicates that an entity has repeatedly or characteristically experienced or exhibited a particular condition, behavior, or event over a significant period in the past.
-
D.
isMajorDamOf
Indicates that one dam is the primary or most significant dam associated with a particular river, reservoir, or water system.
-
E.
notableDisasterType
Indicates the specific kind or category of disaster for which something (such as a place, event, or entity) is notable or best known.
- 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_69e288be2c288190a3a46006945557f7 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d769f7248190ae145218fb0e8bbd |
completed | April 29, 2026, 10:03 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:53 p.m.