Triple
T21285026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alblasserwaard |
E524632
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Langerak |
—
|
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: Langerak | Statement: [Alblasserwaard, contains, Langerak]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Langerak Context triple: [Alblasserwaard, contains, Langerak]
-
A.
Langerak
chosen
Langerak is a small village in the Dutch province of South Holland, known for its rural character and location along the Lek River.
-
B.
Staaken
Staaken is a locality in western Berlin, Germany, known for its residential areas and historical role as part of the Spandau district near the former inner-German border.
-
C.
Lingewaal
Lingewaal was a former municipality in the Dutch province of Gelderland, known for encompassing several rural villages along the river Linge.
-
D.
Kortenberg
Kortenberg is a municipality in the Flemish Brabant province of Belgium, located between Brussels and Leuven and known for its residential character and green surroundings.
-
E.
Elingaard
Elingaard is a historic estate and former manor located in the municipality of Rygge in southeastern Norway.
- 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_69e0b5171f6c8190a5d57201ede73811 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e736d658e08190ad2f267123d53ede |
completed | April 21, 2026, 8:35 a.m. |
Created at: April 16, 2026, 4:03 p.m.