Triple
T31078098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arch of Septimius Severus |
E792025
|
entity |
| Predicate | damnatioMemoriaeOf |
P114169
|
FINISHED |
| Object | Geta |
—
|
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: Geta | Statement: [Arch of Septimius Severus, damnatioMemoriaeOf, Geta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: damnatioMemoriaeOf Context triple: [Arch of Septimius Severus, damnatioMemoriaeOf, Geta]
-
A.
deathEmpire
Indicates a relationship where an empire causes, is associated with, or is characterized by widespread death or destruction.
-
B.
sacrificedBy
Indicates that an entity has been given up, killed, or offered as a sacrifice by another entity.
-
C.
erasesMemoriesOf
chosen
Indicates that one entity causes the memories of another entity to be removed or wiped out.
-
D.
deathBlame
Indicates that responsibility or fault for a death is attributed by one party to another.
-
E.
memorialization
Indicates the act of preserving the memory or honoring the legacy of someone or something, often through a dedicated object, event, or practice.
- 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695bbbaa081909fb1aa003e864c08 |
completed | May 3, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
Created at: April 29, 2026, 9:02 p.m.