Triple
T23149035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of Diana on the Aventine |
E578270
|
entity |
| Predicate | traditionalFoundationType |
P64261
|
FINISHED |
| Object | royal initiative |
—
|
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: royal initiative | Statement: [Temple of Diana on the Aventine, traditionalFoundationType, royal initiative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalFoundationType Context triple: [Temple of Diana on the Aventine, traditionalFoundationType, royal initiative]
-
A.
foundationType
Indicates the structural or organizational basis on which something is built, established, or supported.
-
B.
originalFoundationType
chosen
Indicates the type or nature of the initial foundational structure or base on which something was first established or built.
-
C.
foundationMaterial
Indicates the material from which the foundation or base of something is constructed.
-
D.
architectureType
Indicates the specific style or category of architecture that characterizes or defines an entity.
-
E.
traditionalBase
Indicates that one entity serves as the customary or historically established foundation or basis for another.
- 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_69e245fb8de081908f0eba7b5fd75bc4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18ed0b76c8190ac61b949d88e9970 |
completed | April 29, 2026, 4:53 a.m. |
| PD | Predicate disambiguation | batch_69ef89f83b108190aaaa1db6221fc163 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:01 p.m.