Triple
T17698794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Law (beast-men’s code) |
E441241
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional legal code |
C24522
|
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 code Context triple: [The Law (beast-men’s code), instanceOf, fictional legal code]
-
A.
set of fictional laws
chosen
A set of fictional laws is a collection of imagined legal rules and principles that govern behavior, rights, and consequences within a constructed narrative world.
-
B.
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.
-
C.
fictional code designation
A fictional code designation is an invented alphanumeric label used within narratives or conceptual systems to identify entities, operations, or technologies without referencing real-world codes.
-
D.
fictional legal person
A fictional legal person is an entity, such as a corporation or organization, that the law recognizes as having legal rights and responsibilities similar to those of a natural person, despite not being a human being.
-
E.
legal code text
A legal code text is a formally structured, authoritative written document that systematically sets out laws, regulations, and rules governing conduct within a specific jurisdiction.
- 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_69d8b9ea20b48190ace88bb46b01e6a9 |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10:04 a.m.