Triple
T12629620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piscina Mirabilis |
E301604
|
entity |
| Predicate | hasArtisticDepictions |
P20066
|
FINISHED |
| Object | subject of paintings and engravings |
—
|
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: subject of paintings and engravings | Statement: [Piscina Mirabilis, hasArtisticDepictions, subject of paintings and engravings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArtisticDepictions Context triple: [Piscina Mirabilis, hasArtisticDepictions, subject of paintings and engravings]
-
A.
hasAllegoricalDepictionsBy
Indicates that one entity is represented through allegorical depictions created by another entity.
-
B.
artisticDepiction
chosen
Indicates that one entity visually represents, portrays, or illustrates another in an artistic medium.
-
C.
hasCulturalDepiction
Indicates that one entity is represented, portrayed, or depicted in the cultural work or expression of another entity.
-
D.
hasNotableWorkDepiction
Indicates that an entity has a notable work in which it is depicted or represented.
-
E.
culturalDepictionBy
Indicates that one entity serves as the creator or source of a cultural representation or portrayal of another entity.
- 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_69d7bdeaf49c8190b13800111fa77ea3 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961ae493481908f82e0d05dce20bd |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960b47130819097e1162ed4fc993a |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:15 p.m.