Triple
T36641530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of the Councils |
E904597
|
entity |
| Predicate | languageOfLiturgyHistorically |
P18499
|
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: [Church of the Councils, languageOfLiturgyHistorically, Greek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfLiturgyHistorically Context triple: [Church of the Councils, languageOfLiturgyHistorically, Greek]
-
A.
usesPrimaryLiturgicalLanguageHistorically
chosen
Indicates that an entity has historically used a particular primary liturgical language in its religious rites or worship practices.
-
B.
languageOfWorship
Indicates the language in which religious worship, rituals, or liturgical practices are conducted.
-
C.
languageOfReligion
Indicates the language in which a particular religion is traditionally expressed, practiced, or documented.
-
D.
hasLiturgicalHeritage
Indicates that one entity possesses or is associated with the liturgical tradition, practices, or rites originating from another entity.
-
E.
languageOfScripturalTradition
Indicates the language in which a given scriptural or religious textual tradition is expressed or transmitted.
- 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_69f76e6c63e48190b1d0c3a79a6c7406 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a013f09b0988190ba3179c7d56c726a |
completed | May 11, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_6a013e600e248190a1a9c363702c8586 |
completed | May 11, 2026, 2:26 a.m. |
Created at: May 3, 2026, 4:11 p.m.