Triple
T2777850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arve River |
E61617
|
entity |
| Predicate | passesNear |
P416
|
FINISHED |
| Object | Vernier |
E9287
|
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: Vernier | Statement: [Arve River, passesNear, Vernier]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vernier Context triple: [Arve River, passesNear, Vernier]
-
A.
Vernier
chosen
Vernier is a municipality in the canton of Geneva in southwestern Switzerland, forming part of the Geneva metropolitan area.
-
B.
Elster
Elster is a river in central Europe, primarily flowing through the German state of Saxony and its surrounding regions.
-
C.
Osci
The Osci were an ancient Italic people of southern Italy, closely related to other Campanian tribes and known for their Oscan language and cultural influence in the region.
-
D.
Vane
Vane is an English surname historically associated with several notable aristocratic and political families in Britain.
-
E.
Leister
Leister is a surname of English origin borne by various individuals, including those with the given name Edward.
- 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_69ab4b7e43c48190997b8fc8fb1663ab |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdd83c5fc8190936b971d5577d3f9 |
completed | March 7, 2026, 8:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afc05adf908190bd16bbb6f8ea213a |
completed | March 10, 2026, 6:55 a.m. |
Created at: March 6, 2026, 9:57 p.m.