Triple
T15181515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vésubie |
E362756
|
entity |
| Predicate | flowsThrough |
P225
|
FINISHED |
| Object | Levens |
E362742
|
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: Levens | Statement: [Vésubie, flowsThrough, Levens]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Levens Context triple: [Vésubie, flowsThrough, Levens]
-
A.
Levens
chosen
Levens is a small commune in southeastern France situated in the Alpes-Maritimes department of the Provence-Alpes-Côte d'Azur region.
-
B.
Levens
Levens is a village in Cumbria, England, known for its rural setting near the River Kent and the historic Levens Hall estate.
-
C.
Lievens
Lievens is a Dutch surname most notably associated with the 17th-century painter Jan Lievens, a contemporary and occasional collaborator of Rembrandt.
-
D.
Leven
Leven is a coastal town in eastern Scotland, situated on the Firth of Forth in the council area of Fife.
-
E.
Unsleben
Unsleben is a small municipality in the Rhön-Grabfeld district of northern Bavaria, Germany, known for its rural character and historic village setting.
- 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_69d85a09a39c81908759f23268e2d408 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e006663ad48190986b680001be0e9b |
completed | April 15, 2026, 9:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fec89210e081909e8077fa2487c40e |
completed | May 9, 2026, 5:39 a.m. |
Created at: April 10, 2026, 3:09 a.m.