Triple
T19297601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romanesque art |
E482606
|
entity |
| Predicate | hasSculpturalFeature |
P25695
|
FINISHED |
| Object | tympanum reliefs |
—
|
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: tympanum reliefs | Statement: [Romanesque art, hasSculpturalFeature, tympanum reliefs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSculpturalFeature Context triple: [Romanesque art, hasSculpturalFeature, tympanum reliefs]
-
A.
hasSculpturalFigures
Indicates that something includes or features three-dimensional sculpted figures as part of its form or decoration.
-
B.
hasSculptureType
chosen
Indicates that an entity is associated with a sculpture and specifies the type or category of that sculpture.
-
C.
hasSculptor
Indicates that one entity serves as the sculptor (creator of a sculpture) of another entity.
-
D.
usesSculptureFor
Indicates that one entity employs or utilizes a sculpture for a particular purpose, function, or activity.
-
E.
featuresSculptureOf
Indicates that one entity includes or displays a sculpture that depicts or represents 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fc86f8648190920d122bb141c6e5 |
completed | April 20, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0bc7508190a6f9d56bd4c3404f |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:31 p.m.