Triple
T27802118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Restored Reformed Church |
E702272
|
entity |
| Predicate | primaryAreaOfInfluence |
P104376
|
FINISHED |
| Object | Dutch Bible Belt |
—
|
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 Bible Belt | Statement: [Restored Reformed Church, primaryAreaOfInfluence, Dutch Bible Belt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryAreaOfInfluence Context triple: [Restored Reformed Church, primaryAreaOfInfluence, Dutch Bible Belt]
-
A.
mainTerritoryOfInfluence
chosen
Indicates the primary geographic area where an entity exerts the most significant control, impact, or influence.
-
B.
primaryInfluence
Indicates that one entity serves as the main or most significant influencing factor on another entity’s state, behavior, or outcome.
-
C.
primaryArea
Indicates that one entity is the main or most important area, domain, or field associated with another entity.
-
D.
hasRegionalInfluenceFrom
Indicates that one entity’s influence, impact, or authority in a region is derived from or shaped by another entity.
-
E.
sphereOfInfluence
Indicates the area or domain within which an entity exerts significant control, impact, or authority over others.
- 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_69ef8408e0588190977cffa32dc33a29 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69ff9361943c81909544203cbc998a69 |
completed | May 9, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69ff913138a08190b59bdc9d8d199eb3 |
completed | May 9, 2026, 7:55 p.m. |
Created at: April 27, 2026, 5:35 p.m.