Triple
T33524089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Town of Dorchester |
E858587
|
entity |
| Predicate | religiousOrigins |
P76571
|
FINISHED |
| Object | Puritan |
—
|
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: Puritan | Statement: [Town of Dorchester, religiousOrigins, Puritan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousOrigins Context triple: [Town of Dorchester, religiousOrigins, Puritan]
-
A.
religionAtOrigin
chosen
Indicates that an entity had a particular religion or religious affiliation at the time or place of its origin.
-
B.
religiousMovementOrigin
Indicates that a religious movement began, was founded, or first emerged in a particular place or context.
-
C.
hasReligiousOrigin
Indicates that something originates from, is derived from, or is fundamentally based on a religious tradition, belief system, or practice.
-
D.
religiousTraditions
Indicates a relationship where certain religious customs, practices, or belief systems are associated with or observed by an entity.
-
E.
originReligionContext
Indicates the religious background or setting from which something or someone originates or is derived.
- 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_69f349781c6c819082c516b260efe7e2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff2636e2bc8190bba91eff91431c6e |
completed | May 9, 2026, 12:19 p.m. |
| PD | Predicate disambiguation | batch_69ff25c65be48190868480d94e1c4e89 |
completed | May 9, 2026, 12:17 p.m. |
Created at: May 1, 2026, 1:39 a.m.