Triple
T26936858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allied Military Government in Trieste |
E678408
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | occupation administration |
C7129
|
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: occupation administration Context triple: [Allied Military Government in Trieste, instanceOf, occupation administration]
-
A.
public administration
Public administration is the field and practice of implementing government policies, managing public programs, and coordinating resources and personnel to serve the public interest and promote effective governance.
-
B.
occupation authority office
chosen
An occupation authority office is an administrative body established by a foreign power to govern, regulate, and oversee civil, legal, and economic affairs in a territory under military or political occupation.
-
C.
occupation authority division
Occupation authority division is the organizational structure and allocation of powers among governing bodies or agencies responsible for administering and controlling a territory under military or foreign occupation.
-
D.
occupation authority component
An occupation authority component is a system element responsible for defining, managing, and enforcing rules, permissions, and responsibilities associated with specific roles or professions within an organizational or regulatory context.
-
E.
occupation authority section
An occupation authority section is a designated part of a document or system that defines, records, and manages the official powers, responsibilities, and permissions associated with a specific job or role.
- 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_69eeeb4cac908190a45956c2993d1cc2 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 27, 2026, 6:16 a.m.