Triple
T18085202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steenwijkerland |
E432815
|
entity |
| Predicate | containsSettlement |
P847
|
FINISHED |
| Object | Oldemarkt |
—
|
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: Oldemarkt | Statement: [Steenwijkerland, containsSettlement, Oldemarkt]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oldemarkt Context triple: [Steenwijkerland, containsSettlement, Oldemarkt]
-
A.
Oldemarkt
chosen
Oldemarkt is a village in the Dutch province of Overijssel, known for its traditional character and location within the municipality of Steenwijkerland.
-
B.
Rochusmarkt
Rochusmarkt is a traditional open-air market in Vienna known for its fresh produce, food stalls, and neighborhood atmosphere.
-
C.
Rossmarkt
Rossmarkt is a central public square in Frankfurt am Main known for its historical significance and role as a busy commercial and transit hub.
-
D.
Linden-Markt
Linden-Markt was the original name of Berlin’s historic Gendarmenmarkt square, now renowned for its grand architecture and cultural significance.
-
E.
Ochsenmarkt
Ochsenmarkt was the historical marketplace in Berlin that later became known as Alexanderplatz, once a central hub for trade and urban life.
- 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_69d8b907d05c819083cc3bd6021089e6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4d9fdb00c8190b4769699e94c8941 |
completed | April 19, 2026, 1:34 p.m. |
Created at: April 10, 2026, 10:27 a.m.