Triple
T29887493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | São Sebastião do Rio de Janeiro |
E759055
|
entity |
| Predicate | hasReligionPatron |
P27867
|
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: [São Sebastião do Rio de Janeiro, hasReligionPatron, Roman Catholic Church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligionPatron Context triple: [São Sebastião do Rio de Janeiro, hasReligionPatron, Roman Catholic Church]
-
A.
religiousPatronageIn
Indicates that an entity provides religious patronage, support, or sponsorship within a specified place or region.
-
B.
religiousAffiliationOfPatron
Indicates the religious affiliation or denomination associated with the patron involved in the relationship or action.
-
C.
hasCathedralPatron
Indicates that a person or entity serves as the patron or primary supporter of a particular cathedral.
-
D.
hasReligiousSponsor
Indicates that an entity is financially or organizationally supported by a religious individual, group, or institution.
-
E.
hasAssociatedReligion
chosen
Indicates that an entity is connected with or linked to a particular religion.
- 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_69f2245de2f48190a481404896b56254 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a0031ed5d708190ab93516ad081ada6 |
completed | May 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_6a0031b5dbd081908eb0f4dbb8a0eac3 |
completed | May 10, 2026, 7:20 a.m. |
Created at: April 29, 2026, 6 p.m.