Triple
T6793645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Limburg |
E155996
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Beek |
E537822
|
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: Beek | Statement: [South Limburg, contains, Beek]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Beek Context triple: [South Limburg, contains, Beek]
-
A.
Beek
chosen
Beek is a small municipality in the Dutch province of Limburg, known for hosting Maastricht Aachen Airport and its convenient location near the borders with Belgium and Germany.
-
B.
Zuunbeek
Zuunbeek is a small stream in Belgium that serves as a right-bank tributary of the River Dender.
-
C.
Vierlingsbeek
Vierlingsbeek is a village in the Dutch province of North Brabant, known for its rural character and location along the river Maas.
-
D.
Everbeek
Everbeek is a village in the municipality of Brakel in East Flanders, Belgium, known for its rural landscape and wooded surroundings.
-
E.
Neerpedebeek
Neerpedebeek is a small stream in Belgium that serves as one of the tributaries feeding into the Zenne River.
- 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_69c6881844448190a65822d9b39d7f88 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2af6f908190809e39b73894e513 |
completed | March 27, 2026, 6:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c71a90dfb081909120e8502b26a88b |
completed | March 28, 2026, 12:02 a.m. |
Created at: March 27, 2026, 2:15 p.m.