Triple
T28662515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theatrum Pompeii |
E725503
|
entity |
| Predicate | assassinationSiteOf |
P50073
|
FINISHED |
| Object | Julius Caesar |
—
|
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: Julius Caesar | Statement: [Theatrum Pompeii, assassinationSiteOf, Julius Caesar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assassinationSiteOf Context triple: [Theatrum Pompeii, assassinationSiteOf, Julius Caesar]
-
A.
assassinatedIn
chosen
Indicates that an assassination of one entity occurred within the specified location or context represented by another entity.
-
B.
assassinationAttemptLocation
Indicates the place where an attempted assassination occurred or was intended to occur.
-
C.
placeOfKilling
Indicates the location where a killing event took place.
-
D.
assassinationEvent
Indicates a deliberate killing of a specific individual, typically for political or strategic reasons, carried out as a planned event.
-
E.
notableMassKillingSite
Indicates that a place is recognized as a significant location where a mass killing or massacre 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 4:59 a.m.