Triple
T13048510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Condroz |
E327385
|
entity |
| Predicate | containsSettlement |
P847
|
FINISHED |
| Object | Beauvechain |
E239630
|
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: Beauvechain | Statement: [Condroz, containsSettlement, Beauvechain]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Beauvechain Context triple: [Condroz, containsSettlement, Beauvechain]
-
A.
Beauvechain
chosen
Beauvechain is a municipality in Walloon Brabant, Belgium, known for its rural character and the presence of a major Belgian Air Component base.
-
B.
Gravelotte
Gravelotte is a village in northeastern France best known as the site of a major 1870 Franco-Prussian War battle.
-
C.
Crépy-en-Valois
Crépy-en-Valois is a commune in the Oise department of northern France, known for its historic medieval center and role as a regional rail terminus.
-
D.
Bazeilles
Bazeilles is a commune in northeastern France, historically notable as a battlefield during the Franco-Prussian War.
-
E.
Montmédy
Montmédy is a fortified town in northeastern France near the Luxembourg and Belgian borders, historically significant as the intended royal refuge during the failed Flight to Varennes in 1791.
- 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_69d8076e64308190904fb5c93517c901 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d980b8811c81908577f092e2736610 |
completed | April 10, 2026, 10:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6d5fdd04c8190a86dbba1b81c8e6b |
completed | May 3, 2026, 4:58 a.m. |
Created at: April 9, 2026, 8:57 p.m.