Triple
T29801326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Major Bridgenorth |
E756708
|
entity |
| Predicate | hasReligiousAlignment |
P136960
|
FINISHED |
| Object | Puritanism |
—
|
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: Puritanism | Statement: [Major Bridgenorth, hasReligiousAlignment, Puritanism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligiousAlignment Context triple: [Major Bridgenorth, hasReligiousAlignment, Puritanism]
-
A.
hasReligious
chosen
Indicates that an entity is associated with, practices, or adheres to a particular religion or religious affiliation.
-
B.
hasReligiousType
Indicates that an entity is associated with or classified under a particular religion or religious category.
-
C.
hasAssociatedReligion
Indicates that an entity is connected with or linked to a particular religion.
-
D.
hasReligiousSee
Indicates that one entity serves as the ecclesiastical or religious jurisdiction/seat (see) of another entity.
-
E.
hasReligiousCharacter
Indicates that an entity possesses a religious nature, function, or affiliation, or is characterized by religious aspects or significance.
- 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_69f22454583081908927516cb9938d1d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a002962f6e081909906d6436bae6407 |
completed | May 10, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_6a00284c9c7c8190a77f18a41eee55df |
completed | May 10, 2026, 6:40 a.m. |
Created at: April 29, 2026, 5:18 p.m.