Triple
T32981442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leuenberg Agreement |
E843810
|
entity |
| Predicate | includesChurchesOfTradition |
P3466
|
FINISHED |
| Object | Lutheran |
—
|
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: Lutheran | Statement: [Leuenberg Agreement, includesChurchesOfTradition, Lutheran]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesChurchesOfTradition Context triple: [Leuenberg Agreement, includesChurchesOfTradition, Lutheran]
-
A.
inChristianizedTradition
Indicates that something is understood, practiced, or represented within the context of Christianized religious or cultural tradition.
-
B.
withinChurch
Indicates that one entity is located inside or contained within a church.
-
C.
theologicalTradition
chosen
Indicates the religious or doctrinal school, lineage, or system of belief within which an entity’s theology is developed or practiced.
-
D.
worshipTradition
Indicates that one entity follows, practices, or is associated with a particular religious or spiritual worship tradition.
-
E.
liturgicalTradition
Indicates the specific religious rite or ceremonial tradition according to which a worship service, practice, or community operates.
- 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_69f3494c6f9c8190a255409fce8b1d3b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0226c8b2f881909de3c1a5ba40fc49 |
completed | May 11, 2026, 6:58 p.m. |
| PD | Predicate disambiguation | batch_6a0225602acc8190978ab4aacc615b8d |
completed | May 11, 2026, 6:52 p.m. |
Created at: May 1, 2026, 1:22 a.m.