Triple
T5020061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cornwall |
E112827
|
entity |
| Predicate | hasHistoricReligion |
P7641
|
FINISHED |
| Object | Methodism stronghold |
—
|
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: Methodism stronghold | Statement: [Cornwall, hasHistoricReligion, Methodism stronghold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricReligion Context triple: [Cornwall, hasHistoricReligion, Methodism stronghold]
-
A.
religionHistoricallyAssociated
chosen
Indicates a historical association between an entity and a particular religion, based on past practice, tradition, or cultural linkage rather than current or official status.
-
B.
dominantReligionLegacy
Indicates that a historically dominant religion has left a lasting influence or heritage on a society, culture, or region.
-
C.
hadViewOnReligion
Indicates that an entity held a particular perspective, belief, or stance regarding religion.
-
D.
hasReligiousMovement
Indicates that an entity is associated with, follows, or is characterized by a particular religious movement.
-
E.
hasFormerReligiousJurisdiction
Indicates that an entity was previously under the religious authority or governance of another entity, but no longer is.
- 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_69bd4435c2f48190be593158cbfcf8a3 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7342c62881909acb35849da8761c |
completed | March 20, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69bd714ecfe08190b5830cfc1c74fa17 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:36 p.m.