Triple
T32335525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tower 42 |
E826159
|
entity |
| Predicate | sufferedBombDamage |
P42871
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Tower 42, sufferedBombDamage, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sufferedBombDamage Context triple: [Tower 42, sufferedBombDamage, yes]
-
A.
wasBombedDuring
Indicates that an entity was subjected to a bombing attack during a specified event or time period.
-
B.
wasBombedOn
Indicates that a location or target experienced a bombing event at a specific time or date.
-
C.
bombed
Indicates that one entity attacked another using explosive weapons, causing or intending to cause destruction or damage.
-
D.
sufferedDamageTo
Indicates that one entity has experienced harm, loss, or deterioration affecting another entity or one of its parts.
-
E.
resultOfBombing
chosen
Indicates that something exists or occurs as a consequence or outcome of a bombing event.
- 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_69f34913d9048190befaa634025232be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6be189f848190b9826b97b1191f26 |
completed | May 3, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:48 a.m.