Triple
T18306454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple Bridge |
E438496
|
entity |
| Predicate | locatedInArea |
P40
|
FINISHED |
| Object | Temple Quay |
—
|
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: Temple Quay | Statement: [Temple Bridge, locatedInArea, Temple Quay]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Temple Quay Context triple: [Temple Bridge, locatedInArea, Temple Quay]
-
A.
Temple Quay
chosen
Temple Quay is a modern waterfront business district in central Bristol, England, known for its offices, residential developments, and proximity to major transport links.
-
B.
Centenary Quay
Centenary Quay is a major waterfront residential and mixed-use redevelopment project on the former Vosper Thornycroft shipyard site in Woolston, Southampton.
-
C.
Charter Quay
Charter Quay is a riverside residential and commercial development located in the centre of Kingston upon Thames, England.
-
D.
West End Quay
West End Quay is a modern residential and mixed-use development situated in the regenerated Paddington Basin area of central London.
-
E.
Riverside Quay
Riverside Quay is a dockside area within Hull’s port complex, used for maritime trade and cargo handling along the waterfront.
- 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_69d8b915e3e881909125d760c15d0c29 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5021519a481908a9b6561946f1c65 |
completed | April 19, 2026, 4:25 p.m. |
Created at: April 10, 2026, 10:35 a.m.