Triple
T15053371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oberhausen |
E379422
|
entity |
| Predicate | hasTwinTown |
P919
|
FINISHED |
| Object | Seraing |
E295664
|
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: Seraing | Statement: [Oberhausen, hasTwinTown, Seraing]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Seraing Context triple: [Oberhausen, hasTwinTown, Seraing]
-
A.
Seraing
chosen
Seraing is an industrial city in eastern Belgium known for its steelmaking heritage and location along the Meuse River near Liège.
-
B.
Boesinghe
Boesinghe is a village in West Flanders, Belgium, known for its proximity to key World War I battlefields along the Yser Front.
-
C.
Overijse
Overijse is a municipality in the Flemish Brabant province of Belgium, known for its green residential character and extensive vineyards.
-
D.
Tessenderlo
Tessenderlo is a municipality in the Belgian province of Limburg, known for its chemical industry and location near the Albert Canal.
-
E.
Ougrée
Ougrée is a town in the Walloon region of Belgium that forms a sub-municipality of the industrial city of Seraing in the province of Liège.
- 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_69d85cd64d108190853797a95c11cc45 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69deda92091c81909180f486edf01405 |
completed | April 15, 2026, 12:23 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fea5bdeee48190949b0fe63eb6a21a |
completed | May 9, 2026, 3:10 a.m. |
Created at: April 10, 2026, 3:01 a.m.