Triple
T33634197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richmond (Yorks) constituency |
E861644
|
entity |
| Predicate | hasStrongMilitaryPresence |
P14275
|
FINISHED |
| Object | Catterick Garrison |
—
|
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: Catterick Garrison | Statement: [Richmond (Yorks) constituency, hasStrongMilitaryPresence, Catterick Garrison]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStrongMilitaryPresence Context triple: [Richmond (Yorks) constituency, hasStrongMilitaryPresence, Catterick Garrison]
-
A.
hasMilitaryPresence
chosen
Indicates that a military force is present in, stationed at, or operating within a particular location or entity.
-
B.
hasArmedForces
Indicates that an entity possesses or maintains organized military forces under its control.
-
C.
hasMilitaryBase
Indicates that one entity possesses, hosts, or contains a military base associated with or located on another entity.
-
D.
hasPeacekeepingForcesFrom
Indicates that an entity hosts or is supported by peacekeeping forces that originate from another specified entity.
-
E.
memberNationForces
Indicates that the forces belong to, are contributed by, or are under the authority of a particular member nation.
- 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_69f34981c54c81909b33c3fa2208a52d |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff56ef0a5c8190ae729d66a8cf7fc4 |
completed | May 9, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69ff539859c481909ec56310da418688 |
completed | May 9, 2026, 3:32 p.m. |
Created at: May 1, 2026, 1:41 a.m.