Triple
T3247366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order of Charles III |
E68095
|
entity |
| Predicate | religionAtFoundation |
P4028
|
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: [Order of Charles III, religionAtFoundation, Roman Catholicism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religionAtFoundation Context triple: [Order of Charles III, religionAtFoundation, Roman Catholicism]
-
A.
foundedReligion
Indicates that an entity established or originated a particular religion.
-
B.
religiousAffiliationAtFoundation
chosen
Indicates the religious denomination or tradition with which an entity was affiliated at the time it was founded.
-
C.
dominantReligionLegacy
Indicates that a historically dominant religion has left a lasting influence or heritage on a society, culture, or region.
-
D.
religiousBackgroundOfBase
Indicates the religious background or affiliation associated with a given base or primary entity.
-
E.
traditionalReligionName
Indicates that an entity has a name specifically associated with a traditional or indigenous 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_69ad858e4c708190aa31d486cfee8a6a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaf1c184c8190a43a3594decd0920 |
completed | March 8, 2026, 5:17 p.m. |
| PD | Predicate disambiguation | batch_69ada41837e48190933572165be0ca38 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:09 p.m.