Triple
T6319019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haubourdin |
E141687
|
entity |
| Predicate | river |
P165
|
FINISHED |
| Object | Deûle |
E382455
|
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: Deûle | Statement: [Haubourdin, river, Deûle]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Deûle Context triple: [Haubourdin, river, Deûle]
-
A.
Deûle
chosen
The Deûle is a canalised river in northern France that flows through the Lille metropolitan area and serves as an important waterway for the region.
-
B.
Thieux
Thieux is a small French commune located in the Seine-et-Marne department in the Île-de-France region in north-central France.
-
C.
Smohain
Smohain is a small hamlet in Belgium notable for its proximity to key sites on the Waterloo battlefield.
-
D.
Radaur
Radaur is a town in the Yamunanagar district of Haryana, India, known primarily as a local commercial and educational center for surrounding rural areas.
-
E.
Damphreux
Damphreux is a small municipality in the Ajoie region of the canton of Jura in northwestern Switzerland.
- 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_69c008d13b8c8190be47d896eb735605 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c064c38fe48190a71a4e5e1af19b10 |
completed | March 22, 2026, 9:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c5e48485308190adc2208ad46faaa7 |
completed | March 27, 2026, 1:59 a.m. |
Created at: March 22, 2026, 4:29 p.m.