Triple
T36964797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mobius organization |
E914399
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | multiversal bureaucracy |
C43731
|
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: multiversal bureaucracy Context triple: [Mobius organization, instanceOf, multiversal bureaucracy]
-
A.
administrative union
An administrative union is a collaborative arrangement in which multiple governmental or administrative entities share certain functions, services, or governance structures while retaining their individual legal identities.
-
B.
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.
-
C.
bureaucratic agency
A bureaucratic agency is a formal organizational entity within a government or large institution that implements policies and regulations through standardized procedures, hierarchical authority, and specialized administrative roles.
-
D.
shared universe system
chosen
A shared universe system is a structured framework in which multiple distinct stories, media, or creators coexist and interconnect within a single, consistent fictional world or continuity.
-
E.
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.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:14 p.m.