Triple
T15189254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bebington |
E362961
|
entity |
| Predicate | nearbyCity |
P350
|
FINISHED |
| Object | Liverpool |
E15386
|
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: Liverpool | Statement: [Bebington, nearbyCity, Liverpool]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Liverpool Context triple: [Bebington, nearbyCity, Liverpool]
-
A.
Liverpool
Liverpool is a major suburb and commercial centre in the south-west of Sydney, Australia, known as a key residential, retail, and transport hub in the metropolitan area.
-
B.
Liverpool
chosen
Liverpool is a major port city in northwest England known for its maritime heritage, cultural influence, and role as the birthplace of The Beatles.
-
C.
Liverpool
Liverpool is a residential neighbourhood within the city of Pickering in Ontario, Canada.
-
D.
Manchester
Manchester is a major city in northwest England known for its industrial heritage, vibrant cultural scene, and influential contributions to music, sport, and science.
-
E.
Manchester
Manchester is a historic neighborhood on Pittsburgh’s North Side known for its 19th-century architecture and designation as a historic district.
- 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_69d85a09a39c81908759f23268e2d408 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0067beedc8190abc0a94c7a38f85e |
completed | April 15, 2026, 9:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fed32e425c819083f10f947c258a9b |
completed | May 9, 2026, 6:24 a.m. |
Created at: April 10, 2026, 3:10 a.m.