Triple
T28437155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish resistance liaison missions |
E715298
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | liaison mission |
C5823
|
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: liaison mission Context triple: [Polish resistance liaison missions, instanceOf, liaison mission]
-
A.
military mission
chosen
A military mission is a coordinated operation undertaken by armed forces to achieve specific strategic, operational, or tactical objectives within defined constraints and rules of engagement.
-
B.
liaison officer position
A liaison officer position is a role responsible for facilitating communication, coordination, and collaboration between different organizations, departments, or stakeholder groups to ensure effective information flow and mutual understanding.
-
C.
diplomatic mission unit
A diplomatic mission unit is an organizational subdivision within a diplomatic mission responsible for carrying out specific functions such as political, economic, consular, cultural, or administrative activities in support of a state's foreign relations.
-
D.
multinational mission mechanism
A multinational mission mechanism is a structured framework of processes, agreements, and coordinating bodies that enables multiple countries or organizations to collaboratively plan, resource, and execute a shared mission across borders.
-
E.
former mission
A former mission is a decommissioned or completed organized endeavor, often religious, military, or exploratory, that once pursued a specific objective but is no longer active.
- 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_69efd6b253888190b3c7222ed6a403a8 |
completed | April 27, 2026, 9:35 p.m. |
Created at: April 28, 2026, 1:43 a.m.