Triple
T3901609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patras Cathedral |
E90503
|
entity |
| Predicate | languageOfLiturgicalService |
P45911
|
FINISHED |
| Object | Greek |
—
|
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: Greek | Statement: [Patras Cathedral, languageOfLiturgicalService, Greek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfLiturgicalService Context triple: [Patras Cathedral, languageOfLiturgicalService, Greek]
-
A.
languageOfWorship
Indicates the language in which religious worship, rituals, or liturgical practices are conducted.
-
B.
languageOfCeremony
Indicates the language in which a ceremony is conducted or officially performed.
-
C.
liturgicalLanguageUsage
chosen
Indicates the relationship in which a particular language is used as the medium for conducting religious or liturgical rites, prayers, or ceremonies.
-
D.
liturgicalServices
Indicates that one entity conducts, provides, or is associated with formal acts of public worship or religious rites for another entity or context.
-
E.
usesPrimaryLiturgicalLanguageHistorically
Indicates that an entity has historically used a particular primary liturgical language in its religious rites or worship practices.
- 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_69aed95d315881908cbf1bf4a7215fbf |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1abe2dc81909c18aeae9b286898 |
completed | March 9, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69aee75b5b808190a348a31b1325d3d0 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:21 p.m.