Triple
T29349283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dagenham and Rainham (UK Parliament constituency) |
E744256
|
entity |
| Predicate | borderedByConstituency |
P47257
|
FINISHED |
| Object | Barking (UK Parliament constituency) |
—
|
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: Barking (UK Parliament constituency) | Statement: [Dagenham and Rainham (UK Parliament constituency), borderedByConstituency, Barking (UK Parliament constituency)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderedByConstituency Context triple: [Dagenham and Rainham (UK Parliament constituency), borderedByConstituency, Barking (UK Parliament constituency)]
-
A.
borderingConstituency
chosen
Indicates that one political constituency shares a common boundary with another constituency.
-
B.
isBorderConstituency
Indicates that a constituency lies along or adjacent to a national or regional border.
-
C.
borderingConstituencyState
Indicates that a constituency shares a common boundary with a particular state.
-
D.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
E.
borderingCensusDivision
Indicates that one census division shares a common boundary with another census division.
- 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_69f0a79a2d748190bc30abd469298b37 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fd91a5dad8819093eeeef527027890 |
completed | May 8, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69fd8f65fe9081908902500a3228d935 |
completed | May 8, 2026, 7:23 a.m. |
Created at: April 28, 2026, 2:05 p.m.