Triple
T13214264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hugenottenkirche Erlangen |
E314568
|
entity |
| Predicate | originalLanguageOfWorship |
P18499
|
FINISHED |
| Object | French |
—
|
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: French | Statement: [Hugenottenkirche Erlangen, originalLanguageOfWorship, French]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalLanguageOfWorship Context triple: [Hugenottenkirche Erlangen, originalLanguageOfWorship, French]
-
A.
languageOfWorship
Indicates the language in which religious worship, rituals, or liturgical practices are conducted.
-
B.
liturgicalLanguageVersion
Indicates that one entity is a specific version or form of another entity expressed in a particular liturgical language.
-
C.
languageOfGospelTraditionally
Indicates the language in which a particular Gospel is traditionally believed or held to have been written or transmitted.
-
D.
languageOfCeremony
Indicates the language in which a ceremony is conducted or officially performed.
-
E.
usesPrimaryLiturgicalLanguageHistorically
chosen
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_69d806aee7308190b70a237ba2a6e3e1 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc938f081909f123bdf1263ff7f |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:17 p.m.