Triple
T22600033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Bucks District |
E574788
|
entity |
| Predicate | containsSettlement |
P847
|
FINISHED |
| Object | Iver |
—
|
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: Iver | Statement: [South Bucks District, containsSettlement, Iver]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Iver Context triple: [South Bucks District, containsSettlement, Iver]
-
A.
Iver
Iver is a masculine given name of Norse origin, closely related to the name Ivar and used in various Scandinavian and Germanic countries.
-
B.
Iver
chosen
Iver is a village and civil parish in Buckinghamshire, England, situated near the western edge of Greater London.
-
C.
Ison
Ison is a remote star system in the Star Wars galaxy, located in the Anoat sector and known for its icy, sparsely populated worlds.
-
D.
Isker
Isker was the historic capital city of the Siberian Khanate, serving as its main political and administrative center in western Siberia.
-
E.
Vesle
The Vesle is a river in northeastern France that flows through the Champagne region and was a significant geographic feature during World War I battles.
- 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_69e245bc11308190b69d794d5d1e0bb6 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1626c6ce08190b991e89b12c67a5a |
completed | April 29, 2026, 1:44 a.m. |
Created at: April 17, 2026, 2:50 p.m.