Triple
T17886149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S.T.A.R. Labs |
E447205
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional research organization |
C21880
|
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 research organization Context triple: [S.T.A.R. Labs, instanceOf, fictional research organization]
-
A.
fictional research institution
chosen
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.
-
B.
fictional company
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.
-
C.
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.
-
D.
fictional government ministry
A fictional government ministry is an imagined official department within a government, created in stories or worldbuilding to oversee specific policy areas, functions, or societal needs.
-
E.
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.
- 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_69d8b9f59bd48190a6fc925a855b8bac |
completed | April 10, 2026, 8:51 a.m. |
Created at: April 10, 2026, 10:18 a.m.