Triple
T35860928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Williston |
E1036944
|
entity |
| Predicate | foundingReligiousDenomination |
P4028
|
FINISHED |
| Object | Dutch Reformed Church |
—
|
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: Dutch Reformed Church | Statement: [Williston, foundingReligiousDenomination, Dutch Reformed Church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundingReligiousDenomination Context triple: [Williston, foundingReligiousDenomination, Dutch Reformed Church]
-
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.
religionFoundedOn
Indicates that a particular religion is based on, derived from, or established according to a specific doctrine, text, tradition, or foundational principle.
-
D.
religionOfFoundingFamily
Indicates the religious affiliation practiced or identified with by the family that originally founded an entity.
-
E.
hasReligiousMovementTypeFoundedThere
Indicates that a particular religious movement was founded or originated at the referenced location.
- 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_69f76e1d279c8190843e5b64a0a12c3f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff136ed2a881908f713401083970d1 |
completed | May 9, 2026, 10:58 a.m. |
| PD | Predicate disambiguation | batch_69ff10f9e3448190b6cb6ea5a67713c1 |
completed | May 9, 2026, 10:48 a.m. |
Created at: May 3, 2026, 4:06 p.m.