Triple
T36964824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union (STEM city) |
E914400
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | setting in the Mobius universe |
C47979
|
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: setting in the Mobius universe Context triple: [Union (STEM city), instanceOf, setting in the Mobius universe]
-
A.
entity in a fictional universe
chosen
An entity in a fictional universe is any distinct being, object, or construct that exists within the imagined setting and participates in or is affected by its narrative, rules, and events.
-
B.
region in the Star Wars galaxy
A region in the Star Wars galaxy is a large-scale spatial division of known space, encompassing multiple star systems, sectors, and hyperspace routes that share common political, cultural, or navigational characteristics.
-
C.
Transformers universe location
A Transformers universe location is any distinct place within the Transformers franchise—such as planets, cities, bases, or battlefields—where characters interact, events occur, and stories unfold.
-
D.
location in the Foundation universe
A "location in the Foundation universe" represents any distinct physical or spatial setting—such as planets, space stations, sectors, or regions—within the fictional cosmos of Isaac Asimov’s Foundation series, characterized by its geography, political affiliation, culture, and narrative significance.
-
E.
setting in a video game franchise
The setting in a video game franchise is the recurring fictional world or environment, including its locations, time period, and contextual lore, in which the games’ stories and gameplay take place.
- 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.