Triple
T13253787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nurmijärvi |
E315603
|
entity |
| Predicate | hasBorderWith |
P224
|
FINISHED |
| Object | Loppi |
E782387
|
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: Loppi | Statement: [Nurmijärvi, hasBorderWith, Loppi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Loppi Context triple: [Nurmijärvi, hasBorderWith, Loppi]
-
A.
Loppi
chosen
Loppi is a rural municipality in southern Finland known for its forests, lakes, and traditional village landscapes.
-
B.
Lopik
Lopik is a rural municipality and town in the central Netherlands, known for its agricultural landscape and location along the river Lek.
-
C.
Menapii
The Menapii were an ancient Belgic tribe inhabiting parts of what are now northern France and Belgium, known from Julius Caesar’s accounts of the Gallic Wars.
-
D.
Lipsi
Lipsi is a small Greek island in the southeastern Aegean Sea, known for its tranquil atmosphere, traditional villages, and unspoiled beaches.
-
E.
Loperhet
Loperhet is a coastal commune in the Finistère department of Brittany in northwestern France, situated near the Rade de Brest.
- 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_69d806b1072881909e46bd212259c5f0 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98f7517048190b4eac4e44e81ff66 |
completed | April 11, 2026, 12:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f70a3d6b808190b4ae5225961de03f |
completed | May 3, 2026, 8:41 a.m. |
Created at: April 9, 2026, 9:24 p.m.