Triple
T9074711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Esztergom Basilica |
E217455
|
entity |
| Predicate | hasAltarpieceWidth |
P87052
|
FINISHED |
| Object | about 6.6 meters |
—
|
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: about 6.6 meters | Statement: [Esztergom Basilica, hasAltarpieceWidth, about 6.6 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAltarpieceWidth Context triple: [Esztergom Basilica, hasAltarpieceWidth, about 6.6 meters]
-
A.
hasAltarpiecesInStyle
Indicates that an entity possesses or features altarpieces that are created or designed in a specified artistic style.
-
B.
hasAltar
Indicates that one entity possesses, contains, or includes an altar as part of its features or components.
-
C.
hasIconostasis
Indicates that a place of worship contains or is equipped with an iconostasis, a partition or screen bearing icons that separates different liturgical spaces.
-
D.
hasAltarLocation
Indicates that an altar is situated at or associated with a specific location.
-
E.
heightWithPedestal
Indicates the total vertical measurement of an object including the height of its supporting pedestal.
- 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_69ca83d6c14c8190bc056d927f00a2a2 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc95c4026c8190b553aedb9f4beabb |
completed | April 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69cc65fa79bc81908b46f05c8bba920f |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc6a3c78388190a7436acc0e44ff55 |
completed | April 1, 2026, 12:43 a.m. |
Created at: March 30, 2026, 7:12 p.m.