Triple
T27802041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reformed Political Party |
E702271
|
entity |
| Predicate | supportBaseRegion |
P64159
|
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: [Reformed Political Party, supportBaseRegion, Dutch Bible Belt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportBaseRegion Context triple: [Reformed Political Party, supportBaseRegion, Dutch Bible Belt]
-
A.
supportsRegion
Indicates that one entity provides assistance, resources, or backing to a specific geographic or administrative region.
-
B.
supportBase
Indicates that one entity serves as a foundational or backing structure that physically or functionally supports another entity.
-
C.
hasBaseRegion
chosen
Indicates that one entity is situated upon, supported by, or primarily associated with a specific underlying region or area.
-
D.
homeRegionSupport
Indicates that an entity receives backing, endorsement, or favorable conditions from its own home region or local area.
-
E.
supportArea
Indicates that one entity serves as a supporting region or surface that provides structural or functional backing for another entity.
- 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_6a000fda03948190881b7275f249768f |
completed | May 10, 2026, 4:55 a.m. |
| PD | Predicate disambiguation | batch_6a000f607f1881908ee750d58da91690 |
completed | May 10, 2026, 4:53 a.m. |
Created at: April 27, 2026, 5:35 p.m.