Triple
T2915740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple Quay |
E78601
|
entity |
| Predicate | adjacentTo |
P224
|
FINISHED |
| Object | Redcliffe |
E91975
|
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: Redcliffe | Statement: [Temple Quay, adjacentTo, Redcliffe]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Redcliffe Context triple: [Temple Quay, adjacentTo, Redcliffe]
-
A.
Redcliffe
chosen
Redcliffe is a historic inner-city district of Bristol, England, known for its medieval architecture, harbourside location, and landmarks such as St Mary Redcliffe Church.
-
B.
Brighthelmstone
Brighthelmstone is the historic name of the English coastal town now known as Brighton, a popular seaside resort on the south coast of England.
-
C.
Rippingale
Rippingale is a rural village and civil parish in the South Kesteven district of Lincolnshire, England.
-
D.
Grimston
Grimston is a village and civil parish in the English county of Norfolk, known for its historic church and rural setting near King’s Lynn.
-
E.
Reydon
Reydon is a village and civil parish in the English county of Suffolk, located near the coastal town of Southwold.
- 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_69ad8b0c2ad081909ff87050ae542bb9 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad96a1a9f8819095fe3198e9d3f6b0 |
completed | March 8, 2026, 3:32 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b0562847488190a0d6b7de99796cd9 |
completed | March 10, 2026, 5:34 p.m. |
Created at: March 8, 2026, 2:52 p.m.