Triple
T14711045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maxwell Lord |
E345547
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional businessman |
C4721
|
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 businessman Context triple: [Maxwell Lord, instanceOf, fictional businessman]
-
A.
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.
-
B.
fictionalCharacter
chosen
A fictionalCharacter is an invented person or being in a narrative work, defined by attributes, relationships, and actions that drive the story and embody its themes.
-
C.
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.
-
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.
intelligence-linked businessman
An intelligence-linked businessman is a corporate actor whose commercial activities, investments, or advisory roles are closely intertwined with state or private intelligence operations, often leveraging privileged information networks and covert relationships to advance both strategic and financial objectives.
- 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_69d822e4a8c08190a155df736bb7bc13 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:28 a.m.