Triple
T5396430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort de Joux |
E120667
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Pontarlier |
E448295
|
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: Pontarlier | Statement: [Fort de Joux, locatedNear, Pontarlier]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pontarlier Context triple: [Fort de Joux, locatedNear, Pontarlier]
-
A.
Pontarlier
chosen
Pontarlier is a historic town in eastern France near the Swiss border, known for its role in the absinthe industry and its location in the Jura Mountains.
-
B.
Pougny
Pougny is a small French commune, likely located near the Swiss border in the Auvergne-Rhône-Alpes region.
-
C.
Olbreuse
Olbreuse is a small locality in western France historically notable as the ancestral seat of the noble d’Olbreuse family.
-
D.
Brière
Brière is a French-language surname most prominently associated with former NHL player and current hockey executive Daniel Brière.
-
E.
Plombières
Plombières is a municipality in the province of Liège in eastern Belgium, near the German and Dutch borders.
- 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_69bd4637b92c8190b815b6443ae4b323 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8746f7148190a825736a14baeee1 |
completed | March 20, 2026, 5:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bfb70320ac819088ba3b1da868d9a4 |
completed | March 22, 2026, 9:31 a.m. |
Created at: March 20, 2026, 2:04 p.m.