Triple
T20719126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ancre River |
E509261
|
entity |
| Predicate | flowsThrough |
P225
|
FINISHED |
| Object | Beaucourt-sur-l’Ancre |
—
|
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: Beaucourt-sur-l’Ancre | Statement: [Ancre River, flowsThrough, Beaucourt-sur-l’Ancre]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Beaucourt-sur-l’Ancre Context triple: [Ancre River, flowsThrough, Beaucourt-sur-l’Ancre]
-
A.
Beaucourt
Beaucourt is a small French commune located in the northeastern region of Bourgogne-Franche-Comté near the Swiss border.
-
B.
Bessancourt
Bessancourt is a small suburban commune in the Val-d'Oise department in the Île-de-France region of northern France, forming part of the northwestern outskirts of Paris.
-
C.
Beaucourt-en-Santerre
chosen
Beaucourt-en-Santerre is a small rural commune in the Somme department of northern France, situated within the historical region of Picardy.
-
D.
Breteuil
Breteuil is a commune in northern France that serves as a local administrative and service hub for its surrounding rural area.
-
E.
Juvancourt
Juvancourt is a small commune in the Aube department in north-central France.
- 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_69e0b4c4cc648190b45fda6e2b20af56 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1d39bec8190b3642b0d6d833375 |
completed | April 21, 2026, 12:16 a.m. |
Created at: April 16, 2026, 12:26 p.m.