Triple
T20637771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chapel of the Sacred Heart |
E507130
|
entity |
| Predicate | locatedInChurchType |
P45953
|
FINISHED |
| Object | Jesuit mother 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: Jesuit mother church | Statement: [Chapel of the Sacred Heart, locatedInChurchType, Jesuit mother church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInChurchType Context triple: [Chapel of the Sacred Heart, locatedInChurchType, Jesuit mother church]
-
A.
locatedInTheChurch
Indicates that one entity is physically situated within or inside the church.
-
B.
positionInChurch
Indicates that one entity holds a specific role, office, or rank within a church organization or hierarchy.
-
C.
floorLocationOfChurch
Indicates the specific floor or level within a building where the church is located.
-
D.
hasChurchType
chosen
Indicates that one entity (typically a church) is classified as being of a particular church type or category.
-
E.
roofLocationOfChurch
Indicates that one entity is the roof that belongs to or is located on a church.
- 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_69e0b4be702c8190a3d2410a881d310a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6ad1163008190aa9df36750a952d2 |
completed | April 20, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69e5a0155bd48190b3c769a12cc2c83d |
completed | April 20, 2026, 3:40 a.m. |
Created at: April 16, 2026, 11:42 a.m.