Triple
T13048498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Condroz |
E327385
|
entity |
| Predicate | containsSettlement |
P847
|
FINISHED |
| Object | Ittre |
E696211
|
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: Ittre | Statement: [Condroz, containsSettlement, Ittre]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ittre Context triple: [Condroz, containsSettlement, Ittre]
-
A.
Ittre
chosen
Ittre is a small rural municipality in central Belgium known for its historic village character and location within the province of Walloon Brabant.
-
B.
Dehéries
Dehéries is a small commune in the Nord department of northern France.
-
C.
Dinant
Dinant is a picturesque Belgian town in Wallonia known for its dramatic cliffs along the Meuse River, its citadel, and as the birthplace of saxophone inventor Adolphe Sax.
-
D.
Orgeval
Orgeval is a district in the city of Reims, France, known in part for serving as a terminus of the Reims tramway network.
-
E.
Dumaria
Dumaria is a locality within Bihar's Gaya district in eastern India, known as one of its administrative and inhabited areas.
- 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_69f6cbd8f1308190992c0bd832e1b05e |
completed | May 3, 2026, 4:15 a.m. |
Created at: April 9, 2026, 8:57 p.m.