Triple
T17090714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Opera House, Belfast |
E414716
|
entity |
| Predicate | bombDamage |
P125846
|
FINISHED |
| Object | damaged by bomb attacks in 1991 |
—
|
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: damaged by bomb attacks in 1991 | Statement: [Grand Opera House, Belfast, bombDamage, damaged by bomb attacks in 1991]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bombDamage Context triple: [Grand Opera House, Belfast, bombDamage, damaged by bomb attacks in 1991]
-
A.
bombType
Indicates the specific kind or category of bomb associated with an event, object, or action.
-
B.
bombLoad
Indicates the amount or configuration of bombs carried by an entity, typically an aircraft, for a mission or operation.
-
C.
bombBay
Indicates that an entity serves as or is located in the bomb bay compartment of an aircraft, where bombs are stored and released.
-
D.
warheadEffect
Indicates the type or nature of impact, damage, or outcome produced when a warhead is used or detonated.
-
E.
bombTonnageDropped
Indicates the total weight of bombs that were released or deployed in a given event or context.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbf948d88190a4dd4a0774a8505b |
completed | April 18, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69e35d67b14481909fcdbdeaa5c34785 |
completed | April 18, 2026, 10:31 a.m. |
| PDg | Predicate description generation | batch_69e37542d060819082aa73948eb8ebd4 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:35 a.m.