Triple
T32609241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ipswich West |
E833607
|
entity |
| Predicate | hasBorderingArea |
P37800
|
FINISHED |
| Object | other Ipswich electoral districts |
—
|
LITERAL 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: other Ipswich electoral districts | Statement: [Ipswich West, hasBorderingArea, other Ipswich electoral districts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderingArea Context triple: [Ipswich West, hasBorderingArea, other Ipswich electoral districts]
-
A.
hasBorderAreaStatus
Indicates that an entity has a designated status related to being in or associated with a border area.
-
B.
hasBorderAreaCharacteristics
Indicates that something possesses features or qualities typical of a border area between regions or territories.
-
C.
hasCrossBorderArea
Indicates that an entity is associated with or spans a geographic area that extends across national or jurisdictional borders.
-
D.
hasBorderThrough
Indicates that a border between two regions or entities passes through or along a specified intermediate area, feature, or object.
-
E.
hasBorderRelation
chosen
Indicates that one entity shares a boundary or border with another entity.
- F. None of above.
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_69f3492bfa648190b6ae472074634e29 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
Created at: May 1, 2026, 1:05 a.m.