Triple
T15403913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aisne |
E368397
|
entity |
| Predicate | passesThrough |
P225
|
FINISHED |
| Object | Rethondes |
E126675
|
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: Rethondes | Statement: [Aisne, passesThrough, Rethondes]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rethondes Context triple: [Aisne, passesThrough, Rethondes]
-
A.
Rethondes
chosen
Rethondes is a commune in northern France best known as the site where the World War I armistice was signed in 1918.
-
B.
Teigne
Teigne is the traditional title held by the monarch of the Serer kingdom of Baol in what is now Senegal.
-
C.
Tournelle
Tournelle refers to the historical riverside district and former tower area in Paris that gave its name to the Pont de la Tournelle.
-
D.
Ouffet
Ouffet is a small municipality in the province of Liège in Wallonia, Belgium, known for its rural character and historic village setting.
-
E.
Sauldre
Sauldre is a river in central France that flows through the Cher department and is a tributary of the larger Sauldre river system.
- 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_69d85a16c68c819099c1b547fbc87b32 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e8fde64819082ec0c68df305561 |
completed | April 16, 2026, 1:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff13584f8881908b2527c51f85ae28 |
completed | May 9, 2026, 10:58 a.m. |
Created at: April 10, 2026, 3:19 a.m.