Triple
T9737290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maaseik |
E236095
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Maasland |
E816527
|
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: Maasland | Statement: [Maaseik, locatedIn, Maasland]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Maasland Context triple: [Maaseik, locatedIn, Maasland]
-
A.
Maasland
chosen
Maasland is a historical region in the Low Countries centered along the river Meuse, known for its medieval political and cultural significance.
-
B.
Zoutelande
Zoutelande is a coastal village and popular seaside resort in the Dutch province of Zeeland, known for its beaches and dunes along the North Sea.
-
C.
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.
-
D.
Kennemerland
Kennemerland is a coastal historical region in the northwest of the Netherlands, known for its dunes, beaches, and old trading towns.
-
E.
Foosland
Foosland is a small village located in Champaign County, Illinois, United States.
- 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_69ca84d313e88190983ee6ffd0ef60d2 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9ef032088190acd94c35b89e48b7 |
completed | April 1, 2026, 10:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1afd74a308190ae1a618bab5f7841 |
completed | April 5, 2026, 12:41 a.m. |
Created at: March 30, 2026, 8:22 p.m.