Triple
T26602701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess of Wales's Royal Regiment |
E667678
|
entity |
| Predicate | regimentalHQ |
P36256
|
FINISHED |
| Object | Canterbury |
—
|
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: Canterbury | Statement: [Princess of Wales's Royal Regiment, regimentalHQ, Canterbury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regimentalHQ Context triple: [Princess of Wales's Royal Regiment, regimentalHQ, Canterbury]
-
A.
regimentalCategory
Indicates the classification or type of regiment to which a military unit or formation belongs.
-
B.
regimentalGroup
Indicates that one entity is organized as, or belongs to, a specific regimental-level military group in relation to another entity.
-
C.
garrisonOrHQ
chosen
Indicates that an entity serves as a military garrison or headquarters location for another entity.
-
D.
wasMilitaryHeadquartersOf
Indicates that a place or facility served as the main command center or headquarters for a specific military force or organization.
-
E.
higherRegimentalUnit
Indicates that one military unit is hierarchically subordinate to another, which serves as its higher-level regimental command.
- F. None of above.
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_69ee9cfd20348190bb1255d2603efb7a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f61a17a7788190946f7e32d63cd43f |
completed | May 2, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69f611ab768c8190b1849c15a3e59dda |
completed | May 2, 2026, 3 p.m. |
Created at: April 27, 2026, 2:13 a.m.