Triple
T35647251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Confederado territory |
E1030044
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | in-universe location |
C63513
|
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: in-universe location Context triple: [Confederado territory, instanceOf, in-universe location]
-
A.
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.
-
B.
location in StarCraft universe
A location in the StarCraft universe represents any distinct place—such as a planet, sector, installation, or battlefield—characterized by its lore, environment, strategic significance, and associated factions or events.
-
C.
location in the Avatar universe
A location in the Avatar universe is any distinct place—such as a city, region, landmark, or realm—within the world of Avatar: The Last Airbender and The Legend of Korra that has its own geographic, cultural, or narrative significance.
-
D.
location in The Elder Scrolls universe
A location in The Elder Scrolls universe is any distinct, explorable place—such as cities, dungeons, regions, or landmarks—within the series’ fictional world that can be visited, referenced, or interacted with in-game or in lore.
-
E.
in-universe object
An in-universe object is any tangible or intangible item that exists within a fictional world's reality and can be perceived, used, or referenced by characters in that setting.
- F. None of above. chosen
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_69f76e0938088190a8f199631e97dec3 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:05 p.m.