Triple
T21235878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Orne |
E523340
|
entity |
| Predicate | nearbyVillage |
P4647
|
FINISHED |
| Object | Ranville |
—
|
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: Ranville | Statement: [River Orne, nearbyVillage, Ranville]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ranville Context triple: [River Orne, nearbyVillage, Ranville]
-
A.
Ranville
chosen
Ranville is a village in Normandy, France, notable for its role in the D-Day landings and its proximity to key sites of the 1944 Allied invasion.
-
B.
Le Mesnil-sur-Oger
Le Mesnil-sur-Oger is a renowned Grand Cru village in France’s Champagne region, celebrated for its exceptional Chardonnay-based sparkling wines.
-
C.
Sandouville
Sandouville is a French commune in the Normandy region, known for its industrial activity and proximity to the port city of Le Havre.
-
D.
Tancarville
Tancarville is a commune in northern France best known for the nearby Tancarville Bridge spanning the Seine River and linking the Le Havre region to the rest of Normandy.
-
E.
Nancoury
Nancoury is an alternative name for the Nancowry language, an Austroasiatic language spoken in India’s Nicobar Islands.
- 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_69e0b513b89c81908b27147e91368db2 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e735202c7481909c642ddaafb40671 |
completed | April 21, 2026, 8:28 a.m. |
Created at: April 16, 2026, 3:46 p.m.