Triple
T4259641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Épernay |
E96071
|
entity |
| Predicate | locatedOnRiver |
P165
|
FINISHED |
| Object | Marne River |
E46315
|
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: Marne River | Statement: [Épernay, locatedOnRiver, Marne River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Marne River Context triple: [Épernay, locatedOnRiver, Marne River]
-
A.
Marne
chosen
The Marne is a major river in northeastern France that flows through the Île-de-France region before joining the Seine near Paris.
-
B.
Aube River
The Aube River is a major waterway in northeastern France that flows through the Champagne region before joining the Seine.
-
C.
Vallée de la Marne
Vallée de la Marne is a key subregion of France’s Champagne wine area, known for its vineyards along the Marne River and its significant production of Pinot Meunier–based sparkling wines.
-
D.
Aisne
Aisne is a department in northern France known for its historic towns, World War I battlefields, and rural landscapes.
-
E.
Aisne
Aisne is a river in northeastern France that flows through the Champagne and Picardy regions before joining the Oise River.
- 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_69b3454095ac81909c2494f7ff294af1 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34f7fe7348190baed8d214268b756 |
completed | March 12, 2026, 11:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf3a7a939c8190b8723d3b66130881 |
completed | March 22, 2026, 12:40 a.m. |
Created at: March 12, 2026, 11:06 p.m.