Triple
T34865130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishop of Lund |
E1004988
|
entity |
| Predicate | historicalChurch |
P202528
|
FINISHED |
| Object | Roman 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: Roman Catholic Church | Statement: [Bishop of Lund, historicalChurch, Roman Catholic Church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalChurch Context triple: [Bishop of Lund, historicalChurch, Roman Catholic Church]
-
A.
isHistoricChurchIn
Indicates that a church, recognized as historic, is located within a specified geographic area or jurisdiction.
-
B.
viewOnChurchHistory
Indicates a person's stance, interpretation, or perspective regarding the events, developments, and narratives of church history.
-
C.
hasHistoricChurches
Indicates that an entity possesses or contains one or more churches of recognized historical significance.
-
D.
otherHistoricArchiepiscopalSee
Indicates that an entity has or is associated with another historic archiepiscopal see distinct from its primary one.
-
E.
ecclesiasticalDevelopment
Indicates the process by which religious institutions, doctrines, or practices change, expand, or become more structured over time.
- 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_69f76dbb678081909a247b9b5e1a73ac |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a008d6085508190a71c52cd028a6297 |
completed | May 10, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_6a008ced31448190b8fc60bf87b40647 |
completed | May 10, 2026, 1:49 p.m. |
| PDg | Predicate description generation | batch_6a008d5fe63c8190ab4f5a31c249c674 |
completed | May 10, 2026, 1:51 p.m. |
Created at: May 3, 2026, 4 p.m.