Triple
T26587443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tynemouth (UK Parliament constituency) |
E667246
|
entity |
| Predicate | boundaryReviewArea |
P62086
|
FINISHED |
| Object | North East |
—
|
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: North East | Statement: [Tynemouth (UK Parliament constituency), boundaryReviewArea, North East]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boundaryReviewArea Context triple: [Tynemouth (UK Parliament constituency), boundaryReviewArea, North East]
-
A.
boundaryReviewRegion
chosen
Indicates that a specified region is under consideration or subject to evaluation in a boundary review process.
-
B.
borderArea
Indicates that an area lies along or near the boundary between two regions, countries, or territories.
-
C.
boundaryStatus
Indicates the status or condition of a boundary between entities, such as whether it is defined, active, disputed, or otherwise characterized.
-
D.
boundaryUnit
Indicates that one entity serves as a boundary-defining unit or segment that delimits the extent or limits of another entity.
-
E.
borderRegion
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
- 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_69ee9cfb7e548190b60a9031182f5a7e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f615229fb481909b7fe7d9d17b8604 |
completed | May 2, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 2:06 a.m.