Triple
T1696853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thames Barrier |
E36676
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Woolwich |
E25583
|
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: Woolwich | Statement: [Thames Barrier, near, Woolwich]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Woolwich Context triple: [Thames Barrier, near, Woolwich]
-
A.
Woolwich
chosen
Woolwich is a district in southeast London, England, historically significant as a military and industrial hub along the River Thames.
-
B.
Enfield
Enfield is a historic town in north London that developed from a Middlesex market settlement into a major suburban and commercial center.
-
C.
Enfield
Enfield is a small rural town located in Tompkins County in the Finger Lakes region of New York State.
-
D.
Aldershot
Aldershot is a town in Hampshire, England, historically known as a major British Army garrison and military center.
-
E.
Battersea
Battersea is a district in the London Borough of Wandsworth, known for its riverside location along the Thames, Battersea Power Station, and Battersea Park.
- 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_69a886163dec8190859c514232a37a05 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa62b78d20819096f0602058c46d8a |
completed | March 6, 2026, 5:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69adb5bc1db881908e859dbde2ea2d98 |
completed | March 8, 2026, 5:45 p.m. |
Created at: March 4, 2026, 7:30 p.m.