Triple
T13268352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brock Barracks, Reading |
E315983
|
entity |
| Predicate | significantUnit |
P109230
|
FINISHED |
| Object | Royal Gloucestershire, Berkshire and Wiltshire Regiment |
E795510
|
NE FINISHED |
How this triple was built (3 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: Royal Gloucestershire, Berkshire and Wiltshire Regiment | Statement: [Brock Barracks, Reading, significantUnit, Royal Gloucestershire, Berkshire and Wiltshire Regiment]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Royal Gloucestershire, Berkshire and Wiltshire Regiment Context triple: [Brock Barracks, Reading, significantUnit, Royal Gloucestershire, Berkshire and Wiltshire Regiment]
-
A.
Royal Gloucestershire, Berkshire and Wiltshire Light Infantry
chosen
The Royal Gloucestershire, Berkshire and Wiltshire Light Infantry was a British Army infantry regiment formed from the amalgamation of county regiments, later merged into The Rifles as part of wider army restructuring.
-
B.
Royal Berkshire Regiment
The Royal Berkshire Regiment was an infantry regiment of the British Army with a long history of service in major conflicts, including both World Wars.
-
C.
Royal Hampshire Regiment
The Royal Hampshire Regiment was a historic line infantry regiment of the British Army with origins dating back to the 18th century, known for its distinguished service in numerous major conflicts before its amalgamation in the early 1990s.
-
D.
Duke of Edinburgh's Royal Regiment (Berkshire and Wiltshire)
The Duke of Edinburgh's Royal Regiment (Berkshire and Wiltshire) was a British Army infantry regiment formed in 1959 that served in various global deployments, including Northern Ireland, until its amalgamation into the Royal Gloucestershire, Berkshire and Wiltshire Regiment in 1994.
-
E.
Royal Sussex Regiment
The Royal Sussex Regiment was a historic line infantry regiment of the British Army with roots in Sussex, known for its long service in major conflicts from the 18th through the 20th centuries.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantUnit Context triple: [Brock Barracks, Reading, significantUnit, Royal Gloucestershire, Berkshire and Wiltshire Regiment]
-
A.
designationUnit
Indicates that one entity serves as the unit or standard of measure used to designate, label, or quantify another entity.
-
B.
isMajorUnitOf
Indicates that one unit functions as the primary or principal component within a larger organizational or structural context of another entity.
-
C.
significantPort
Indicates that a port holds major importance in terms of trade, transportation, or strategic relevance within a given context.
-
D.
superunitOf
Indicates that one unit is hierarchically above and directly encompasses another unit within an organizational or structural system.
-
E.
basicUnitOf
Indicates that one entity serves as the fundamental or smallest constituent unit from which the other entity is composed or defined.
- F. None of above. chosen
Provenance (5 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_69d806b1d9ac8190852c5571d5bd5f0f |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f74610b2c481909497296e999226e8 |
completed | May 3, 2026, 12:56 p.m. |
| PD | Predicate disambiguation | batch_69d98f60911081909fa346a054f76c9f |
completed | April 11, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69d99cf7f9c48190a6a4f452b4a2aefa |
completed | April 11, 2026, 12:59 a.m. |
Created at: April 9, 2026, 9:26 p.m.