Triple
T4475165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tidworth Camp |
E99989
|
entity |
| Predicate | hasGarrisonRole |
P17521
|
FINISHED |
| Object | armoured warfare |
—
|
LITERAL 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: armoured warfare | Statement: [Tidworth Camp, hasGarrisonRole, armoured warfare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGarrisonRole Context triple: [Tidworth Camp, hasGarrisonRole, armoured warfare]
-
A.
garrisonedUnit
Indicates that one unit is stationed inside, occupying, or defending another entity such as a building, vehicle, or fortification.
-
B.
garrisonCommander
Indicates that one entity serves as the commanding officer in charge of the military garrison located at or associated with another entity.
-
C.
previousGarrison
Indicates that one entity served as the earlier or former garrison location or stationed force for another entity.
-
D.
garrisonDuty
Indicates a relationship where an entity is assigned to stay and defend or guard a specific location as part of its military or protective duties.
-
E.
garrisonType
chosen
Indicates the specific kind or classification of military garrison associated with an entity.
- 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_69b34553cbe48190afa8ac1cac285b86 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35728ed508190ba0e882fa62d8848 |
completed | March 13, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69b3563d63008190816e37027e761375 |
completed | March 13, 2026, 12:11 a.m. |
Created at: March 12, 2026, 11:35 p.m.