Triple
T3866908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zuid-Beijerland |
E91880
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Piershil |
E353559
|
NE FINISHED |
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: Piershil | Statement: [Zuid-Beijerland, locatedNear, Piershil]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Piershil Context triple: [Zuid-Beijerland, locatedNear, Piershil]
-
A.
Piershil
chosen
Piershil is a small village in the Dutch province of South Holland, known for its rural character and location on the island of Hoeksche Waard.
-
B.
Polyanka
Polyanka is a Moscow Metro station on the Serpukhovsko–Timiryazevskaya Line, located near the city center and serving the surrounding Polyanka Street area.
-
C.
Oreshek
Oreshek is the historic Russian fortress on Lake Ladoga that later gave rise to the town of Shlisselburg.
-
D.
Patori
Patori is a small town located in the Samastipur district of the Indian state of Bihar.
-
E.
Rytro
Rytro is a village in southern Poland’s Lesser Poland Voivodeship, situated in the scenic Poprad Valley of the Western Carpathians and known as a local tourist and hiking destination.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69aed9645f348190a9868e7cef56ab7e |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec3b8d988190b56d42ac1521e19c |
completed | March 9, 2026, 3:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b512410f38819089adccf0a476dd8f |
completed | March 14, 2026, 7:46 a.m. |
Created at: March 9, 2026, 3:19 p.m.