Triple
T22981754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Project Wildfire |
E571486
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional government installation |
C14870
|
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: fictional government installation Context triple: [Project Wildfire, instanceOf, fictional government installation]
-
A.
fictional political institution
A fictional political institution is an imagined organization or governing body within a narrative world that creates, interprets, or enforces rules, policies, or power structures for story purposes.
-
B.
fictional government ministry
A fictional government ministry is an imagined official department within a government, created in stories or worldbuilding to oversee specific policy areas, functions, or societal needs.
-
C.
fictional interstellar government
A fictional interstellar government is a large-scale political organization that exerts authority, creates laws, and manages relations across multiple planets, star systems, or galaxies within a speculative universe.
-
D.
fictional research institution
A fictional research institution is an imagined organization dedicated to conducting systematic investigation and experimentation, often serving as a setting or driver for scientific, technological, or societal developments within a narrative.
-
E.
intelligence agency facility
chosen
An intelligence agency facility is a secure, specialized complex where classified information is collected, analyzed, stored, and operations are coordinated to support national security and intelligence objectives.
- 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_69e245b3c50481908bb3741ec9f40862 |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:49 p.m.