Triple
T15723985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian cruiser Bolzano |
E381174
|
entity |
| Predicate | dateDamagedSeverely |
P13733
|
FINISHED |
| Object | 25 August 1942 |
—
|
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: 25 August 1942 | Statement: [Italian cruiser Bolzano, dateDamagedSeverely, 25 August 1942]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateDamagedSeverely Context triple: [Italian cruiser Bolzano, dateDamagedSeverely, 25 August 1942]
-
A.
damagedIn
Indicates that an entity has suffered harm, impairment, or destruction as a result of a specified event, process, or condition.
-
B.
damageYear
Indicates the year in which the damage to an entity occurred or was recorded.
-
C.
damagedBy
Indicates that one entity has caused harm, impairment, or deterioration to another entity.
-
D.
damagedWorkBy
Indicates that one entity has caused harm, impairment, or destruction to a work created by another entity.
-
E.
dateOfLoss
chosen
Indicates the specific date on which a loss event (such as damage, theft, or other covered incident) occurred.
- 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_69d86d9cdb648190bf3171be0bd7d872 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04fb1fdd4819088f3e243263e5f73 |
completed | April 16, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69e00526759c819088b80d85138b8974 |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:46 a.m.