Triple
T31078097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arch of Septimius Severus |
E792025
|
entity |
| Predicate | inscriptionAlteredBy |
P170717
|
FINISHED |
| Object | erasure of Geta’s name |
—
|
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: erasure of Geta’s name | Statement: [Arch of Septimius Severus, inscriptionAlteredBy, erasure of Geta’s name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inscriptionAlteredBy Context triple: [Arch of Septimius Severus, inscriptionAlteredBy, erasure of Geta’s name]
-
A.
inscriptionAlteredIn
chosen
Indicates that an inscription has been modified, altered, or changed within a specified context, time, or event.
-
B.
inscriptionBy
Indicates that an inscription was created, written, or carved by a particular agent or entity.
-
C.
inscriptionVariant
Indicates that one inscription is a variant form or version of another inscription, differing in content, wording, or presentation while remaining closely related.
-
D.
inscription
Indicates that text has been written, carved, or engraved onto a surface or object.
-
E.
inscriptionSide
Indicates the specific side or face of an object on which an inscription is located.
- 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_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:02 p.m.