Triple
T11907533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Himalayan Escapes |
E283308
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional expedition company |
C7523
|
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 expedition company Context triple: [Himalayan Escapes, instanceOf, fictional expedition company]
-
A.
fictional company
chosen
A fictional company is an imagined business entity created for storytelling, simulation, or illustrative purposes, complete with its own brand, structure, and operations but without real-world legal or commercial existence.
-
B.
fictional space exploration organization
A fictional space exploration organization is an imagined institution—such as an agency, corporation, or coalition—dedicated to planning, funding, and conducting missions beyond Earth for purposes like discovery, colonization, defense, or scientific advancement.
-
C.
fictional group
A fictional group is an imagined collection of characters or entities, defined by shared traits, goals, or context, that exists only within a narrative or creative work.
-
D.
fictional empire
A fictional empire is a large, often expansionist and hierarchical political entity in a fictional setting, characterized by centralized authority, distinct culture, and influence over multiple regions or peoples.
-
E.
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.
- 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:44 p.m.