Triple
T12958428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Wall |
E310076
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | structure in A Song of Ice and Fire |
C4771
|
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: structure in A Song of Ice and Fire Context triple: [The Wall, instanceOf, structure in A Song of Ice and Fire]
-
A.
organization in A Song of Ice and Fire
An organization in A Song of Ice and Fire is a structured group of individuals—such as noble houses, religious orders, military factions, or secret societies—united by shared goals, loyalties, and rules that influence political, social, and military dynamics in Westeros and beyond.
-
B.
organization in Game of Thrones
An organization in Game of Thrones is a structured group of individuals united by a common purpose, hierarchy, and set of rules or traditions that influence political, military, religious, or social power within the world of Westeros and beyond.
-
C.
structure
chosen
A structure is an organized arrangement of interrelated components or elements designed to support, contain, or give form to something within a particular context.
-
D.
character group in Tolkien legendarium
A character group in the Tolkien legendarium is a collection of individuals—such as races, cultures, or fellowships—united by shared lineage, purpose, or identity within the mythic world of Middle-earth and beyond.
-
E.
military structure
A military structure is an organized framework of ranks, units, and command relationships that defines how armed forces are arranged, governed, and coordinated to conduct operations.
- 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_69d7bdfb57a88190836b743e2825feca |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:44 p.m.