Triple
T20553489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soesterberg Air Base |
E504656
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Soesterberg |
—
|
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: Soesterberg | Statement: [Soesterberg Air Base, locatedIn, Soesterberg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Soesterberg Context triple: [Soesterberg Air Base, locatedIn, Soesterberg]
-
A.
Soesterberg
chosen
Soesterberg is a village in the Dutch province of Utrecht known for its historic military air base and long-standing association with the Royal Netherlands Air Force.
-
B.
De Vliedberg
De Vliedberg is a residential neighborhood located within the Dutch municipality of Hellevoetsluis in South Holland.
-
C.
Zandbergen
Zandbergen is a village in East Flanders, Belgium, that forms part of the municipality of Geraardsbergen.
-
D.
Zandbergen
Zandbergen is a small hamlet in the municipality of Losser in the province of Overijssel in the eastern Netherlands.
-
E.
Woudenberg
Woudenberg is a small Dutch municipality and town located in the central Netherlands.
- 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_69e0b4b52c048190952b4d0f430813a3 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a5db052c8190801e53f6148113c8 |
completed | April 20, 2026, 10:16 p.m. |
Created at: April 16, 2026, 11:38 a.m.