Triple
T38255409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Folkung |
E1017774
|
entity |
| Predicate | usedReligionForLegitimacy |
P76551
|
FINISHED |
| Object | Catholic Church |
—
|
NE NERFINISHED |
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: Catholic Church | Statement: [House of Folkung, usedReligionForLegitimacy, Catholic Church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedReligionForLegitimacy Context triple: [House of Folkung, usedReligionForLegitimacy, Catholic Church]
-
A.
religiousLegitimation
Indicates that something is justified, authorized, or validated by reference to religious beliefs, doctrines, or institutions.
-
B.
usedReligionFor
chosen
Indicates that an entity employed religion as a means or tool to achieve some purpose, goal, or effect.
-
C.
isUsedByReligion
Indicates that something (such as an object, practice, text, or symbol) is employed or utilized within the context of a particular religion.
-
D.
religiousClaim
Indicates that an entity asserts, expresses, or is associated with a statement or belief grounded in religion or spiritual doctrine.
-
E.
reveredByReligion
Indicates that a religion holds a particular entity in high esteem, veneration, or sacred regard.
- 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_69f76de33e4481909099fa812709bd42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.