Triple
T8954761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mariazell Basilica |
E213444
|
entity |
| Predicate | mainRelic |
P18543
|
FINISHED |
| Object | miraculous wooden statue of the Virgin Mary |
—
|
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: miraculous wooden statue of the Virgin Mary | Statement: [Mariazell Basilica, mainRelic, miraculous wooden statue of the Virgin Mary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainRelic Context triple: [Mariazell Basilica, mainRelic, miraculous wooden statue of the Virgin Mary]
-
A.
containsRelic
chosen
Indicates that one entity holds, includes, or has within it a relic.
-
B.
notableRelic
Indicates that an entity is a historically or culturally significant relic associated with another entity (such as a place, person, or event).
-
C.
hasRelicsStatus
Indicates that an entity holds a particular status or condition specifically related to relics.
-
D.
hasRelicType
Indicates that an entity is associated with, classified by, or possesses a specific type or category of relic.
-
E.
relicsLocatedIn
Indicates that certain relics are situated, stored, or found within a specific location.
- 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_69ca8399ad2081909f8fa41d4314c215 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6724f3e4819092c6b13d80871e80 |
completed | April 1, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed74d288190b712d739805579dc |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7 p.m.