Triple
T3311531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Long Ashton |
E69583
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Bristol |
E16444
|
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: Bristol | Statement: [Long Ashton, locatedNear, Bristol]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bristol Context triple: [Long Ashton, locatedNear, Bristol]
-
A.
Bristol
chosen
Bristol is a historic port city in southwest England known for its maritime heritage, vibrant cultural scene, and distinctive Georgian and Victorian architecture.
-
B.
Bath
Bath is a historic city in Somerset, England, renowned for its Roman-built baths and Georgian architecture.
-
C.
Bath
Bath is a small town located in the parish of St. Thomas in the East in eastern Jamaica, known historically for its mineral springs and colonial-era significance.
-
D.
Brighton
Brighton is a small city in Colorado that forms part of the Denver metropolitan area along the Front Range of the Rocky Mountains.
-
E.
Brighton
Brighton is a small mountain resort town in Utah known for its ski area, alpine scenery, and outdoor recreation.
- 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_69ad859f218081909458d2cebbf57565 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0ec80508190baa78435b983b7b5 |
completed | March 8, 2026, 5:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b3606f413c8190b3f8e5e8fcaa6878 |
completed | March 13, 2026, 12:55 a.m. |
Created at: March 8, 2026, 3:11 p.m.