Triple
T15467010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 4 PARA |
E372055
|
entity |
| Predicate | garrison |
P75
|
FINISHED |
| Object | Hebburn |
E62417
|
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: Hebburn | Statement: [4 PARA, garrison, Hebburn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hebburn Context triple: [4 PARA, garrison, Hebburn]
-
A.
North Shields
North Shields is a coastal town on the north bank of the River Tyne in North East England, historically known for its fishing and shipbuilding industries.
-
B.
Wansbeck
Wansbeck is a UK parliamentary constituency in Northumberland that includes the town of Ashington and surrounding communities in northeast England.
-
C.
Benwell
Benwell is a residential district in the west end of Newcastle upon Tyne, England, known for its historical industrial roots and subsequent urban regeneration.
-
D.
South Shields
South Shields is a coastal town in Tyne and Wear, England, known historically for its shipbuilding and as part of the Tyneside urban area.
-
E.
Hebburn-on-Tyne, England
chosen
Hebburn-on-Tyne, England is an industrial town on the River Tyne historically known for its shipbuilding and marine engineering industries.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f69a31c81909a749247b6615d91 |
completed | April 16, 2026, 1:46 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff2d01a23c819095cf75b7d5a801a9 |
completed | May 9, 2026, 12:48 p.m. |
Created at: April 10, 2026, 3:33 a.m.