Triple
T7996394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bible Belt of the Netherlands |
E186136
|
entity |
| Predicate | notableMunicipality |
P41762
|
FINISHED |
| Object | Staphorst |
—
|
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: Staphorst | Statement: [Bible Belt of the Netherlands, notableMunicipality, Staphorst]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableMunicipality Context triple: [Bible Belt of the Netherlands, notableMunicipality, Staphorst]
-
A.
notableRegionOfSettlement
Indicates that a specified region is a significant or prominent place where an entity is or has been settled.
-
B.
notableInCity
Indicates that an entity is particularly prominent, recognized, or significant within a specific city.
-
C.
notableCityIncluded
chosen
Indicates that a notable or significant city is contained within, or is part of, a larger geographic or administrative entity.
-
D.
notableLocality
Indicates that a locality (such as a city, town, or region) is notably associated with, or significant to, the subject entity.
-
E.
specialMunicipality
Indicates that an entity is designated as a special municipality, typically having a distinct administrative or legal status compared to regular municipalities.
- 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_69ca829c6c308190ab05b43d234c52b2 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c97968481908d261b3f0bd6b8e6 |
completed | March 31, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69cb0483d3b48190b250c7603d747bca |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:17 p.m.