Triple
T22275175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hohne Garrison |
E550581
|
entity |
| Predicate | garrisonedUnitType |
P114791
|
FINISHED |
| Object | armoured regiment |
—
|
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 regiment | Statement: [Hohne Garrison, garrisonedUnitType, armoured regiment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: garrisonedUnitType Context triple: [Hohne Garrison, garrisonedUnitType, armoured regiment]
-
A.
garrisonedUnit
Indicates that one unit is stationed inside, occupying, or defending another entity such as a building, vehicle, or fortification.
-
B.
garrisonType
Indicates the specific kind or classification of military garrison associated with an entity.
-
C.
garrisonForceType
chosen
Indicates the specific type or classification of military force assigned to occupy, defend, or maintain control of a particular location.
-
D.
garrisonedForce
Indicates that a military force is stationed in and occupies a specific location, typically for defense or control.
-
E.
garrisonOrCrewType
Indicates the specific kind of garrison or crew assigned to occupy, staff, or operate a given 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_69e11e43d8208190aff4f9cf7f2c2a8a |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f14ea643d48190985371d01aac7bfc |
completed | April 29, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:40 p.m.