Triple
T34892110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milton Security |
E1006313
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional private security firm |
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 private security firm Context triple: [Milton Security, instanceOf, fictional private security firm]
-
A.
fictional criminal enterprise
A fictional criminal enterprise is an imagined, organized group engaged in illegal activities within a narrative, serving as a central source of conflict, intrigue, and moral tension.
-
B.
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.
-
C.
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.
-
D.
fictional organization in the Terminator franchise
A fictional organization in the Terminator franchise is a structured group—such as Skynet, Resistance cells, or corporate and military entities—whose members, goals, and resources drive the conflict between humans and machines across different timelines.
-
E.
fictional corporate office
A fictional corporate office is an imagined workplace setting that represents the structure, culture, and daily operations of a business organization, often used as a backdrop for storytelling, satire, or exploration of professional dynamics.
- 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_69f76dbfe5788190ad8b64f241f470c8 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4 p.m.