Triple
T13039298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crown as corporation sole |
E326646
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional legal person |
C32380
|
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 legal person Context triple: [Crown as corporation sole, instanceOf, fictional legal person]
-
A.
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.
-
B.
fictional persona
A fictional persona is an invented character with distinct traits, background, and motivations, created to embody perspectives or roles within a narrative or conceptual context.
-
C.
fictional legal document
A fictional legal document is an invented text that mimics the structure, language, and authority of real legal instruments (such as contracts, statutes, or court opinions) for use within a narrative, game, or speculative scenario.
-
D.
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.
-
E.
fictional barristers’ chambers
A fictional barristers’ chambers is an imagined collective of self-employed specialist advocates sharing premises, clerks, and professional culture, used as a setting to explore legal practice, courtroom drama, and interpersonal dynamics within the bar.
- 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_69d8076cc45c81908123123f43e69266 |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 8:55 p.m.