Triple
T21902839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lopik |
E540853
|
entity |
| Predicate | containsSettlement |
P847
|
FINISHED |
| Object | Lopik (village) |
—
|
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: Lopik (village) | Statement: [Lopik, containsSettlement, Lopik (village)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lopik (village) Context triple: [Lopik, containsSettlement, Lopik (village)]
-
A.
Lopik (village)
chosen
Lopik (village) is a small settlement in the Dutch province of Utrecht that serves as the main population center and namesake of the surrounding municipality of Lopik.
-
B.
Sukeva village
Sukeva village is a small settlement in Finland known primarily for housing the Sukevan vankila prison.
-
C.
Laupa village
Laupa village is a small rural settlement located in Järva County in central Estonia.
-
D.
Myrskylä village
Myrskylä village is a small rural settlement in eastern Uusimaa, Finland, serving as the administrative and service center of the surrounding Myrskylä municipality.
-
E.
Jõelähtme village
Jõelähtme village is a small rural settlement in northern Estonia known for its historic church and scenic natural surroundings.
- 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_69e0c47b4e8c81908c8076eaa4c8e4f2 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f121d2d63c819090e115708aa4dbf8 |
completed | April 28, 2026, 9:08 p.m. |
Created at: April 16, 2026, 7:24 p.m.