Triple
T34276689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archbishop of Aparecida |
E879475
|
entity |
| Predicate | associatedWithCountryPatronage |
P17912
|
FINISHED |
| Object | Brazil |
E19289
|
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: Brazil | Statement: [Archbishop of Aparecida, associatedWithCountryPatronage, Brazil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithCountryPatronage Context triple: [Archbishop of Aparecida, associatedWithCountryPatronage, Brazil]
-
A.
countryOfPatronage
chosen
Indicates the country that officially supports, sponsors, or acts as a patron for a given entity or activity.
-
B.
hasPatronageOver
Indicates that one entity serves as a patron, sponsor, or protector for another, exercising support, guidance, or authority over it.
-
C.
sharesPatronageWith
Indicates that two entities are supported, sponsored, or funded by the same patron or sponsoring party.
-
D.
patronessOfCountry
Indicates that a female patron (often a saint or protective figure) serves as the spiritual or symbolic guardian of a specific country.
-
E.
associatedWithNationality
Indicates that one entity has a connection or affiliation with the nationality of 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_69f349b5f6648190b9420d94a4cd16e0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36f9bdbb988190adf392adf25f8bb9 |
completed | June 20, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:56 a.m.