Triple
T8954749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mariazell Basilica |
E213444
|
entity |
| Predicate | foundingLegendDate |
P85854
|
FINISHED |
| Object | 1157 |
—
|
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: 1157 | Statement: [Mariazell Basilica, foundingLegendDate, 1157]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundingLegendDate Context triple: [Mariazell Basilica, foundingLegendDate, 1157]
-
A.
foundingAround
Indicates that an entity was founded at approximately, but not exactly, the specified time or within a loosely defined surrounding period.
-
B.
foundedOn
Indicates that an entity was established, created, or brought into existence on a specific date or point in time.
-
C.
foundingOf
Indicates the event or relationship in which an entity is established or created, typically linking the founder(s), the founded entity, and the time or context of its creation.
-
D.
foundedBefore
Indicates that one entity was established or created at an earlier time than the other entity.
-
E.
isFoundedOn
Indicates that one entity is established, created, or based upon another entity as its foundational source or principle.
- 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_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. |
| PDg | Predicate description generation | batch_69cc5f887108819096d45a186fc137b3 |
completed | March 31, 2026, 11:58 p.m. |
Created at: March 30, 2026, 7 p.m.