Triple
T4186989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armistice of 22 June 1940 |
E88335
|
entity |
| Predicate | locationSigned |
P441
|
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: [Armistice of 22 June 1940, locationSigned, Rethondes]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rethondes Context triple: [Armistice of 22 June 1940, locationSigned, 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.
Sauldre
Sauldre is a river in central France that flows through the Cher department and is a tributary of the larger Sauldre river system.
-
C.
Yerre
The Yerre is a river in northern France that flows through the Île-de-France region before joining the Loir.
-
D.
Fasquelle
Fasquelle is a French publishing house known for issuing notable literary and scholarly works.
-
E.
Anières
Anières is a small lakeside municipality in western Switzerland, situated on the shores of Lake Geneva near the city of Geneva.
- 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_69aed9477e8c81908bcb862d2db55b1d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af032490888190bbfa422003caca99 |
completed | March 9, 2026, 5:28 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b58a00e3308190b4fbed211069204a |
completed | March 14, 2026, 4:17 p.m. |
Created at: March 9, 2026, 3:45 p.m.