Triple
T11326847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gouvy |
E268242
|
entity |
| Predicate | hasSettlement |
P1068
|
FINISHED |
| Object | Gouvy (village) |
E268242
|
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: Gouvy (village) | Statement: [Gouvy, hasSettlement, Gouvy (village)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gouvy (village) Context triple: [Gouvy, hasSettlement, Gouvy (village)]
-
A.
Gouvy
chosen
Gouvy is a rural municipality in the Belgian province of Luxembourg, known for its natural landscapes and proximity to the Ardennes region.
-
B.
Gourbesville
Gourbesville is a small rural commune in the Manche department of northwestern France, situated in the Normandy region.
-
C.
Poulainville
Poulainville is a small commune in northern France located in the Somme department of the Hauts-de-France region.
-
D.
Souvigny
Souvigny is a historic town in central France known for its important Cluniac priory and medieval religious heritage.
-
E.
Prévondavaux
Prévondavaux is a small municipality in the canton of Fribourg in western 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9e2253881909518cad0f12ef612 |
completed | April 9, 2026, 6:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e52608b7348190875597513ca1a995 |
completed | April 19, 2026, 6:59 p.m. |
Created at: April 8, 2026, 9:32 p.m.