Triple

T22828994
Position Surface form Disambiguated ID Type / Status
Subject 42 Commando E565745 entity
Predicate garrison P75 FINISHED
Object Bickleigh Barracks NE NERFINISHED

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: Bickleigh Barracks | Statement: [42 Commando, garrison, Bickleigh Barracks]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bickleigh Barracks
Context triple: [42 Commando, garrison, Bickleigh Barracks]
  • A. Bickleigh Barracks chosen
    Bickleigh Barracks is a Royal Marines military base in Devon, England, best known as the long-standing home of 42 Commando.
  • B. Stonehouse Barracks
    Stonehouse Barracks is a historic Royal Marines military installation located in Plymouth, England.
  • C. Battlesbury Barracks
    Battlesbury Barracks is a British Army installation near Warminster in Wiltshire, England, used primarily as a base for infantry units and training activities.
  • D. Tern Hill Barracks
    Tern Hill Barracks is a British Army installation in Shropshire, England, historically used as a military base and training facility.
  • E. Osborn Barracks
    Osborn Barracks is a military installation in Hong Kong used by the People’s Liberation Army as part of its local garrison.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e24585ab1c81909b2b5065d15805d5 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17e2a0e308190941064965346f890 completed April 29, 2026, 3:42 a.m.
Created at: April 17, 2026, 3:34 p.m.