Triple
T2161688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bulgarian Greek Catholic Church |
E46813
|
entity |
| Predicate | hasMarriedPriesthoodTradition |
P36088
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Bulgarian Greek Catholic Church, hasMarriedPriesthoodTradition, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMarriedPriesthoodTradition Context triple: [Bulgarian Greek Catholic Church, hasMarriedPriesthoodTradition, true]
-
A.
hasSpouseInTradition
Indicates that one entity is recognized as the spouse of another according to a specified cultural, religious, or legal tradition.
-
B.
marriageToProphetOccurredIn
Indicates that the marriage to the prophet took place in a specified location or context.
-
C.
wasMarriedBeforeProphet
Indicates that a person had been married at least once prior to the time of becoming a prophet.
-
D.
allowsDivorcedRemarriedCommunion
Indicates that an authority or practice permits individuals who are divorced and remarried to receive communion.
-
E.
marriageType
Indicates the specific legal or social category of a marriage relationship that exists between two spouses.
- F. None of above. chosen
Provenance (4 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_69a88a184cbc8190877791f6552c2484 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbe89e6ac8190b4b4bc0be4fe7aa9 |
completed | March 7, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69abbd9c90408190b6b65498ca43ce26 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbe1ecb7081909c2c66da08a48ab7 |
completed | March 7, 2026, 5:56 a.m. |
Created at: March 4, 2026, 7:45 p.m.