Triple
T84601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Eucharist |
E1701
|
entity |
| Predicate | consideredOrdinanceBy |
P3099
|
FINISHED |
| Object | many Protestant churches |
—
|
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: many Protestant churches | Statement: [Holy Eucharist, consideredOrdinanceBy, many Protestant churches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consideredOrdinanceBy Context triple: [Holy Eucharist, consideredOrdinanceBy, many Protestant churches]
-
A.
recognizedAsOrdinanceBy
chosen
Indicates that something is formally acknowledged or accepted as an ordinance by a particular authority or governing body.
-
B.
enactedBy
Indicates that a law, policy, or formal measure is officially established or brought into effect by a specific authority or governing body.
-
C.
codifiedIn
Indicates that something is formally recorded, defined, or established within a specific document, code, or legal/institutional text.
-
D.
considered
Indicates that one entity regards, judges, or thinks about another entity in a particular way or context.
-
E.
enactedInResponseTo
Indicates that one action, policy, or measure was carried out as a direct reaction to a specific prior event, condition, or stimulus.
- 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_69a24c8150408190910a693eb51c1f71 |
completed | Feb. 28, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69a24f4e73c081908d2da146226ef05e |
completed | Feb. 28, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69a24eb469548190b38c24e81f36c838 |
completed | Feb. 28, 2026, 2:11 a.m. |
Created at: Feb. 28, 2026, 2:06 a.m.