Triple
T20885305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oldambt |
E514261
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Scheemda |
—
|
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: Scheemda | Statement: [Oldambt, contains, Scheemda]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Scheemda Context triple: [Oldambt, contains, Scheemda]
-
A.
Scheemda
chosen
Scheemda is a village in the municipality of Oldambt in the province of Groningen in the northeastern Netherlands.
-
B.
Wessum
Wessum is a village and district within the town of Ahaus in the state of North Rhine-Westphalia, Germany.
-
C.
Langeveen
Langeveen is a small village in the Dutch province of Overijssel, located within the municipality of Tubbergen.
-
D.
Eemshaven
Eemshaven is a major seaport and energy hub in the north of the Netherlands, known for its power plants, data centers, and offshore wind connections.
-
E.
Veendam
Veendam is a town and municipality in the province of Groningen in the northeastern Netherlands, historically known for peat extraction and later for its industrial development.
- 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_69e0b4f733f081908a401c0b7beb0b9f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c67c9d1c81908031eb77c124f119 |
completed | April 21, 2026, 12:36 a.m. |
Created at: April 16, 2026, 12:46 p.m.