Triple
T25219269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 26th Army |
E631915
|
entity |
| Predicate | garrisonOrAreaOfResponsibility |
P32851
|
FINISHED |
| Object | Karelian region |
—
|
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: Karelian region | Statement: [26th Army, garrisonOrAreaOfResponsibility, Karelian region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: garrisonOrAreaOfResponsibility Context triple: [26th Army, garrisonOrAreaOfResponsibility, Karelian region]
-
A.
garrisonOrRecruitmentArea
Indicates an area designated for stationing military forces or for recruiting personnel into those forces.
-
B.
garrisonOrAssemblyArea
Indicates a location where military forces are stationed, housed, or gathered for organization, preparation, or deployment.
-
C.
garrisonRegion
chosen
Indicates that a military force is stationed in and responsible for defending a specific region.
-
D.
garrisonOrHQ
Indicates that an entity serves as a military garrison or headquarters location for another entity.
-
E.
garrisonOrMobilizationPoint
Indicates a location where military forces are stationed, assembled, or prepared for deployment or mobilization.
- 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_69e75a8e0f688190a7aebe9a4815e25b |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f47b914fe08190b104ecc2583ce1f7 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f44d849e7c81909945438f40e35362 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 21, 2026, 1:02 p.m.