Triple
T35766175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of Augustus and Rome |
E1034020
|
entity |
| Predicate | discoveryOfInscription |
P31851
|
FINISHED |
| Object | 16th century |
—
|
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: 16th century | Statement: [Temple of Augustus and Rome, discoveryOfInscription, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveryOfInscription Context triple: [Temple of Augustus and Rome, discoveryOfInscription, 16th century]
-
A.
inscriptionsFoundAt
chosen
Indicates that inscriptions are discovered or located at a particular place or site.
-
B.
attestedInInscriptions
Indicates that evidence for the entity is documented or recorded in one or more inscriptions.
-
C.
pyramidTextInscriptions
Indicates that the subject has text inscriptions located on or within a pyramid.
-
D.
notableInscriptionBy
Indicates that an inscription of particular note or significance on an entity was created, authored, or carved by a specified agent.
-
E.
mainContentOfInscriptions
Indicates that something represents the primary textual or symbolic content conveyed by a set of inscriptions.
- 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_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:06 p.m.