Triple
T1629586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sacred Heart Cathedral |
E35225
|
entity |
| Predicate | hasAltars |
P15258
|
FINISHED |
| Object | multiple side altars |
—
|
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: multiple side altars | Statement: [Sacred Heart Cathedral, hasAltars, multiple side altars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAltars Context triple: [Sacred Heart Cathedral, hasAltars, multiple side altars]
-
A.
hasAltar
chosen
Indicates that one entity possesses, contains, or includes an altar as part of its features or components.
-
B.
hasShrinesIn
Indicates that one entity possesses or maintains shrines that are located within the area or domain of another entity.
-
C.
enshrines
Indicates that one entity formally preserves, protects, or honors another by giving it a permanent, often sacred or legally recognized, status.
-
D.
worshippedIn
Indicates that a particular deity, figure, or object of reverence is the focus of religious or spiritual worship within a specified place or context.
-
E.
hasDeity
Indicates that one entity recognizes, worships, or is associated with another entity as its deity or divine figure.
- 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_69a886036bc081909ff5de16dbe5e8ea |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9431af5ac8190893133f1ae490142 |
completed | March 5, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69a907c91c888190b6ed295c1a2e0977 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.