Triple
T7479787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Catholic churches |
E176720
|
entity |
| Predicate | mayBeDesignatedAs |
P974
|
FINISHED |
| Object | parish church |
—
|
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: parish church | Statement: [Roman Catholic churches, mayBeDesignatedAs, parish church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeDesignatedAs Context triple: [Roman Catholic churches, mayBeDesignatedAs, parish church]
-
A.
canBeDesignatedBy
Indicates that one entity is capable of being assigned, labeled, or identified by another entity as its designation.
-
B.
isDesignatedRight
Indicates that something has been formally assigned or recognized as the correct or official right in a given context.
-
C.
hasDesignation
chosen
Indicates that an entity holds or is assigned a specific title, label, or formal designation.
-
D.
hasDesignationBy
Indicates that one entity has been formally assigned or labeled with a specific designation by another entity.
-
E.
decisionMakerForDesignation
Indicates that one entity has the authority or responsibility to make or approve decisions regarding the designation or assignment of another entity.
- 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_69c69f236ce08190a04d7679f03b29b2 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f532f4488190b6edaa96099c3b8f |
completed | March 27, 2026, 9:22 p.m. |
| PD | Predicate disambiguation | batch_69c6f03d967081908a8e696ff9693b90 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:42 p.m.