Triple
T14415145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guaratinguetá |
E357430
|
entity |
| Predicate | religionImportantFor |
P6906
|
FINISHED |
| Object | Roman Catholicism |
—
|
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: Roman Catholicism | Statement: [Guaratinguetá, religionImportantFor, Roman Catholicism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religionImportantFor Context triple: [Guaratinguetá, religionImportantFor, Roman Catholicism]
-
A.
religionSignificant
chosen
Indicates that a particular religion plays an important or influential role in relation to the referenced entity or context.
-
B.
isCentralToReligion
Indicates that something plays a core, defining, or foundational role within a particular religion or religious tradition.
-
C.
usedReligionFor
Indicates that an entity employed religion as a means or tool to achieve some purpose, goal, or effect.
-
D.
majorReligionCanBe
Indicates that an entity can have a particular major religion as one of its possible primary religious affiliations.
-
E.
religionOrBelief
Indicates that one entity holds, practices, or is associated with a particular religion, faith, or belief system.
- 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de90cc99208190a2313b1acfb5d802 |
completed | April 14, 2026, 7:09 p.m. |
| PD | Predicate disambiguation | batch_69de5c30467881908e770e3940295641 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:17 a.m.