Triple
T30931572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Loves of the Gods |
E788004
|
entity |
| Predicate | architecturalFramework |
P159124
|
FINISHED |
| Object | quadratura |
—
|
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: quadratura | Statement: [The Loves of the Gods, architecturalFramework, quadratura]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: architecturalFramework Context triple: [The Loves of the Gods, architecturalFramework, quadratura]
-
A.
architecturalConcept
Indicates that one entity represents or embodies an architectural concept in relation to another entity.
-
B.
exampleArchitecture
chosen
Indicates that one entity serves as a representative or illustrative instance of the architectural style, structure, or design of another entity.
-
C.
architectureName
Indicates the specific name or title assigned to an architecture.
-
D.
frameworkFor
Indicates that one entity serves as a supporting structure, system, or basis that organizes, guides, or enables the development or functioning of another entity.
-
E.
toArchitecture
Indicates a relationship in which something is designed, structured, or organized according to a particular architectural style, plan, or system.
- 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_69f224c0b7fc819090cb89df60d23653 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 29, 2026, 8:52 p.m.