Triple
T4028042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lisbon Military Region |
E83639
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military region |
C13035
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: military region Context triple: [Lisbon Military Region, instanceOf, military region]
-
A.
military administrative division
chosen
A military administrative division is a geographically defined area organized under a specific command structure to manage, coordinate, and support military operations, logistics, and governance within its boundaries.
-
B.
Geographic combatant command
A geographic combatant command is a unified military command responsible for planning and conducting operations within a specific, defined region of the world.
-
C.
military organization
A military organization is a structured group of armed forces personnel and resources, organized under a defined hierarchy and command system, to plan, coordinate, and conduct defense and combat operations in support of a state’s strategic objectives.
-
D.
military unit
A military unit is an organized group of armed personnel structured under a defined command hierarchy to perform specific tactical or operational missions.
-
E.
military campaign theater
A military campaign theater is a geographically defined area where coordinated military operations and strategies are conducted to achieve specific objectives within a broader conflict.
- F. None of above.
Provenance (1 batch)
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_69aed92e29ac819080f7a98b594fec05 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:36 p.m.