Triple
T9827839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wehrkreis VI staff |
E238701
|
entity |
| Predicate | militaryDistrictNumber |
P2804
|
FINISHED |
| Object | VI |
—
|
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: VI | Statement: [Wehrkreis VI staff, militaryDistrictNumber, VI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryDistrictNumber Context triple: [Wehrkreis VI staff, militaryDistrictNumber, VI]
-
A.
militaryDistrict
chosen
Indicates that an entity functions as, or is located within, an administrative military district or region under military jurisdiction.
-
B.
federalDistrictNumber
Indicates the specific numbered federal electoral or administrative district associated with an entity.
-
C.
regimentalNumber
Indicates the unique identifying number assigned to a member of a regiment, linking an individual to their specific regimental record.
-
D.
headquartersDistrict
Indicates the administrative district or area where an organization’s main headquarters is located.
-
E.
hasMunicipalDistrictNumber
Indicates that a municipality or local administrative unit is assigned a specific district number within its municipal structure.
- 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_69ca84e0dd1881909800765d1e21f735 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb324e7848190b9424a78ca653afe |
completed | April 2, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cd03e30bc08190816c0a6d29c21b0f |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:32 p.m.