Triple
T22728968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stampersgat |
E562074
|
entity |
| Predicate | hasRoadAccessTo |
P22549
|
FINISHED |
| Object | Fijnaart |
—
|
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: Fijnaart | Statement: [Stampersgat, hasRoadAccessTo, Fijnaart]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fijnaart Context triple: [Stampersgat, hasRoadAccessTo, Fijnaart]
-
A.
Fijnaart
chosen
Fijnaart is a village in the Dutch province of North Brabant, known for its rural character and location within the municipality of Moerdijk.
-
B.
Rijkevorsel
Rijkevorsel is a municipality in the Antwerp province of Belgium, located in the historic Kempen (Campine) region.
-
C.
Flandersbach
Flandersbach is a district of the town of Wülfrath in North Rhine-Westphalia, Germany.
-
D.
Maasgouw
Maasgouw is a municipality in the Dutch province of Limburg, known for its historic villages and location along the river Maas.
-
E.
Landsmeer
Landsmeer is a small Dutch town and municipality in North Holland, situated just north of Amsterdam and known for its watery landscapes and nature reserves.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e24550859c81908727d91efc3a81b4 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1792be7d88190b6d7d79041fcba25 |
completed | April 29, 2026, 3:21 a.m. |
Created at: April 17, 2026, 3:21 p.m.