Triple
T1492244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Onex |
E29604
|
entity |
| Predicate | borderedBy |
P224
|
FINISHED |
| Object | Bernex |
E53379
|
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: Bernex | Statement: [Onex, borderedBy, Bernex]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bernex Context triple: [Onex, borderedBy, Bernex]
-
A.
Bernex
chosen
Bernex is a municipality in western Switzerland located near the city of Geneva, known for its semi-rural character and surrounding vineyards.
-
B.
Berner
A Berner is a resident or native of the Swiss city of Bern.
-
C.
Arlon
Arlon is a historic town in southeastern Belgium that serves as the capital of the province of Luxembourg in the Walloon Region.
-
D.
Cologny
Cologny is an affluent municipality on the shores of Lake Geneva in Switzerland, known for its scenic views and as the home of the World Economic Forum’s headquarters.
-
E.
Porrentruy
Porrentruy is a historic town in northwestern Switzerland known for its medieval castle and role as a regional center in the canton of Jura.
- 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_69a498dba1d8819093b46a3a8d2485f1 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c6c4f0c88190a97ba4910c1a5d85 |
completed | March 1, 2026, 11:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad2943545c8190a2246a41d712528b |
completed | March 8, 2026, 7:46 a.m. |
Created at: March 1, 2026, 8:12 p.m.