Triple
T31790047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gniezno Cathedral |
E811437
|
entity |
| Predicate | GnieznoDoorsDepict |
P172301
|
FINISHED |
| Object | life of Saint Adalbert |
—
|
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: life of Saint Adalbert | Statement: [Gniezno Cathedral, GnieznoDoorsDepict, life of Saint Adalbert]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: GnieznoDoorsDepict Context triple: [Gniezno Cathedral, GnieznoDoorsDepict, life of Saint Adalbert]
-
A.
bronzeDoorsBy
Indicates that an entity is the creator, designer, or responsible agent for a set of bronze doors.
-
B.
doorwayFeature
Indicates that one entity is a feature, characteristic, or structural element specifically associated with a doorway of another entity.
-
C.
doorSymbol
Indicates a symbolic representation that denotes or marks the presence or concept of a door.
-
D.
shieldDepicts
Indicates that a shield bears or displays a particular image, symbol, or design as its depiction.
-
E.
doorKeyMotif
Indicates a recurring thematic relationship where doors and keys symbolically interact, such as keys granting access through doors or doors representing thresholds unlocked by keys.
- F. None of above. chosen
Provenance (4 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_69f348e60748819082dcaa7792659803 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ac186f888190979084647ec49b6a |
completed | May 3, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69f6aa21f2508190a204a424ffc00ca6 |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aac95c1481909fff33702d0a6c37 |
completed | May 3, 2026, 1:54 a.m. |
Created at: April 30, 2026, 11:38 p.m.