Triple
T21518548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Towns of Connecticut |
E530908
|
entity |
| Predicate | religiousBackgroundOfManySettlers |
P102028
|
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: [River Towns of Connecticut, religiousBackgroundOfManySettlers, Puritan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousBackgroundOfManySettlers Context triple: [River Towns of Connecticut, religiousBackgroundOfManySettlers, Puritan]
-
A.
religiousBackgroundOfCommunity
Indicates the religious tradition, affiliation, or belief system that characterizes or predominates within a particular community.
-
B.
religionOfColonists
chosen
Indicates the religious affiliation practiced or imposed by colonizing groups in a given colonial context.
-
C.
religiousBackgroundOfBase
Indicates the religious background or affiliation associated with a given base or primary entity.
-
D.
settlerOf
Indicates that an entity established or inhabited a place as a settler of that location.
-
E.
earlySettlers
Indicates that the associated entities were among the first people to inhabit or establish a community in a particular area.
- 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_69e0c45d95a081908e7962ad215da746 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee81438cbc8190aba0f546b27eb2a4 |
completed | April 26, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e6320043bc81909417c41a718652ba |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:25 p.m.