Triple
T6057178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of Jupiter Optimus Maximus |
E134941
|
entity |
| Predicate | againDestroyedBy |
P5325
|
FINISHED |
| Object | fire in AD 69 |
—
|
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: fire in AD 69 | Statement: [Temple of Jupiter Optimus Maximus, againDestroyedBy, fire in AD 69]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: againDestroyedBy Context triple: [Temple of Jupiter Optimus Maximus, againDestroyedBy, fire in AD 69]
-
A.
destroyedDuring
Indicates that one entity was destroyed in the course of, or as a consequence of, a specified event or time period.
-
B.
damagedBy
Indicates that one entity has caused harm, impairment, or deterioration to another entity.
-
C.
sufferedDestructionOf
Indicates that one entity experienced damage, ruin, or loss as a result of the destruction of another entity.
-
D.
hasCauseOfDestruction
chosen
Indicates that one entity is the cause or agent responsible for the destruction or damage of another entity.
-
E.
typeOfDestruction
Indicates the specific manner or method by which something is destroyed or caused to cease to exist.
- 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_69c00877b6d4819096b0e163728b73a3 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0570d00e88190b2d8d596e40378d9 |
completed | March 22, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69c049edc6f0819092ca620d9073ad26 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:09 p.m.