Triple
T30063360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bavaria and Styria |
E763957
|
entity |
| Predicate | haveCulturalLinksIn |
P38730
|
FINISHED |
| Object | Catholic traditions |
—
|
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: Catholic traditions | Statement: [Bavaria and Styria, haveCulturalLinksIn, Catholic traditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveCulturalLinksIn Context triple: [Bavaria and Styria, haveCulturalLinksIn, Catholic traditions]
-
A.
hasCulturalHeritageLink
Indicates a relationship where one entity is culturally derived from, influenced by, or historically connected to another.
-
B.
hasCulturalRelation
chosen
Indicates a relationship in which entities are connected through shared, influencing, or interacting cultural practices, values, traditions, or expressions.
-
C.
hasCulturalEventLink
Indicates a relationship where an entity is associated with a link or reference to a related cultural event.
-
D.
hasAssociatedCulture
Indicates that an entity is related to, influenced by, or characterized by a particular culture.
-
E.
hasCulturalScope
Indicates that a relationship or action is limited to, relevant within, or characterized by a particular cultural context or domain.
- 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_69f2247221388190a13a22c47094a0ef |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ca4dc388190a6f3cf48f2fad819 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 6:58 p.m.