Triple
T18841628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lajoux |
E460810
|
entity |
| Predicate | neighboringMunicipality |
P17964
|
FINISHED |
| Object | Saicourt |
—
|
NE NERFINISHED |
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: Saicourt | Statement: [Lajoux, neighboringMunicipality, Saicourt]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Saicourt Context triple: [Lajoux, neighboringMunicipality, Saicourt]
-
A.
Saicourt
chosen
Saicourt is a small municipality in the French-speaking Jura bernois region of the canton of Bern in Switzerland.
-
B.
Longueville
Longueville is a historical French territorial domain associated with the noble House of Orléans-Longueville.
-
C.
Longueville
Longueville is a harbourside residential suburb on Sydney’s Lower North Shore, known for its waterfront views and affluent, leafy streets.
-
D.
La Guéroulde
La Guéroulde is a small commune in northern France, located in the Eure department of the Normandy region.
-
E.
Souchon
Souchon is a German surname most notably associated with Admiral Wilhelm Souchon, a key naval commander during World War I.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5b8ea35c88190af6659551ad18130 |
completed | April 20, 2026, 5:26 a.m. |
Created at: April 10, 2026, 11:56 a.m.