Triple
T12009818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Night's Watch |
E285877
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | organization in A Song of Ice and Fire |
C29896
|
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: organization in A Song of Ice and Fire Context triple: [Night's Watch, instanceOf, organization in A Song of Ice and Fire]
-
A.
Star Wars organization
A Star Wars organization is a structured group or faction within the Star Wars universe, defined by a common purpose, ideology, or function that influences galactic events and character relationships.
-
B.
Gallifreyan organization
A Gallifreyan organization is a structured collective of Time Lords and associated entities from the planet Gallifrey, formed to govern, regulate, or influence temporal affairs and societal functions within Time Lord civilization.
-
C.
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.
-
D.
group of characters in Middle-earth
A group of characters in Middle-earth is a collection of individuals—such as Hobbits, Elves, Dwarves, Men, or other beings—who are connected by shared purpose, lineage, culture, or circumstance within Tolkien’s fictional world.
-
E.
object in Tolkien legendarium
An object in the Tolkien legendarium is any physical or crafted item—mundane or magical—that exists within Tolkien’s fictional world and can be used, possessed, or referenced by its characters.
- 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_69d6ab45a368819084fce08bf0dc3705 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:46 p.m.