Triple
T34525334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Good Jesus |
E886383
|
entity |
| Predicate | hasFeastOrShrine |
P21389
|
FINISHED |
| Object | Sanctuary of Bom Jesus do Monte |
E647839
|
NE 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: Sanctuary of Bom Jesus do Monte | Statement: [Good Jesus, hasFeastOrShrine, Sanctuary of Bom Jesus do Monte]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFeastOrShrine Context triple: [Good Jesus, hasFeastOrShrine, Sanctuary of Bom Jesus do Monte]
-
A.
hasPilgrimageOrFeast
Indicates that there is a religious pilgrimage or feast associated with, dedicated to, or occurring in relation to the referenced entity.
-
B.
hasShrinesIn
Indicates that one entity possesses or maintains shrines that are located within the area or domain of another entity.
-
C.
hasShrines
Indicates that one entity contains, hosts, or is associated with one or more shrines dedicated to another entity.
-
D.
hasAssociatedFeast
Indicates that something (such as a person, event, or entity) is linked to a specific feast or celebratory religious observance.
-
E.
hasMajorShrine
chosen
Indicates that one entity serves as a principal or primary shrine dedicated to another entity.
- F. None of above.
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_69f349cd7c148190aa99192b126d1527 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3740fb377881908b10da9dd800dc93 |
completed | June 21, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 1, 2026, 2:02 a.m.