Triple
T13842029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fresnes-sur-Marne |
E332681
|
entity |
| Predicate | sharesBorderWith |
P224
|
FINISHED |
| Object | Charny |
E332680
|
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: Charny | Statement: [Fresnes-sur-Marne, sharesBorderWith, Charny]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Charny Context triple: [Fresnes-sur-Marne, sharesBorderWith, Charny]
-
A.
Charny
chosen
Charny is a French commune located in the Île-de-France region, known for its rural character within the greater Paris metropolitan area.
-
B.
Charroux
Charroux is a historic commune in western France known for its medieval heritage and the remains of its once-prominent Benedictine abbey.
-
C.
Rebecq
Rebecq is a municipality in the Belgian province of Walloon Brabant, known for its rural character and historic watermills.
-
D.
Douaumont
Douaumont is a small commune in northeastern France best known for its World War I battlefield sites near Verdun, including major memorials and military cemeteries.
-
E.
Livarchamps
Livarchamps is a small village in the municipality of Vaux-sur-Sûre in the Walloon region of Belgium.
- 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_69d81c5ba13c8190839315f54768acfd |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02afce788190a74dce4e6a3569fa |
completed | April 14, 2026, 9:02 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7c0ef9e7c8190b96c2b83d04708e1 |
completed | May 3, 2026, 9:41 p.m. |
Created at: April 9, 2026, 10:13 p.m.