Triple
T31790048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gniezno Cathedral |
E811437
|
entity |
| Predicate | GnieznoDoorsDate |
P164851
|
FINISHED |
| Object | 12th century |
—
|
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: 12th century | Statement: [Gniezno Cathedral, GnieznoDoorsDate, 12th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: GnieznoDoorsDate Context triple: [Gniezno Cathedral, GnieznoDoorsDate, 12th century]
-
A.
GnieznoDoorsDepict
Indicates that something (such as an artwork, text, or representation) portrays or shows scenes related to the Gniezno Doors.
-
B.
bronzeDoorsDate
chosen
Indicates the date or time period associated with the creation, installation, or use of the bronze doors.
-
C.
bronzeDoorsBy
Indicates that an entity is the creator, designer, or responsible agent for a set of bronze doors.
-
D.
mainPortalDate
Indicates the primary or official date associated with a portal’s main event, status, or activation.
-
E.
roofDecorationDate
Indicates the date on which a roof decoration was created, installed, or completed.
- 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_69f348e60748819082dcaa7792659803 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:38 p.m.