Triple
T16945819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boroughbridge |
E411065
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Aldborough |
E85296
|
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: Aldborough | Statement: [Boroughbridge, near, Aldborough]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Aldborough Context triple: [Boroughbridge, near, Aldborough]
-
A.
Aldborough
chosen
Aldborough was a former parliamentary borough in England that historically returned members to the British House of Commons.
-
B.
Corbridge
Corbridge is a historic village in Northumberland, England, known for its Roman heritage and picturesque setting on the banks of the River Tyne.
-
C.
Glevum
Glevum was the Roman-era name for the settlement that later became the English city of Gloucester, originally established as a military fort and later developed into a colonia.
-
D.
Eboracum
Eboracum was the major Roman fortress and city that later became the English city of York, serving as an important military and administrative center in Roman Britain.
-
E.
Bremetennacum
Bremetennacum was a Roman fort and settlement in northern Britain, located near modern-day Ribchester in Lancashire.
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cfb14b788190be5b7f9c00c3e7ea |
completed | April 18, 2026, 6:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00d46036108190a3ed8cb9f80c47fb |
completed | May 10, 2026, 6:54 p.m. |
Created at: April 10, 2026, 5:31 a.m.