Triple
T35766145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of Augustus and Rome |
E1034020
|
entity |
| Predicate | inscriptionTitle |
P128561
|
FINISHED |
| Object | Res Gestae Divi Augusti |
—
|
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: Res Gestae Divi Augusti | Statement: [Temple of Augustus and Rome, inscriptionTitle, Res Gestae Divi Augusti]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inscriptionTitle Context triple: [Temple of Augustus and Rome, inscriptionTitle, Res Gestae Divi Augusti]
-
A.
inscriptionHonors
Indicates that an inscription is created to honor, commemorate, or pay tribute to a particular entity or event.
-
B.
hasTitleInInscription
Indicates that an entity is mentioned with a specific title or designation within an inscription.
-
C.
inscriptionKnownAs
chosen
Indicates that an inscription is referred to or identified by a particular name, label, or designation.
-
D.
inscriptionType
Indicates the specific kind or category of inscription associated with an entity (e.g., dedicatory, funerary, commemorative).
-
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_69f76e13edd081909101629aa829c4ad |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.