Triple
T36036725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anderson Financial Management |
E1042423
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional financial advisory 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 financial advisory firm Context triple: [Anderson Financial Management, instanceOf, fictional financial advisory firm]
-
A.
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.
-
B.
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.
-
C.
trading firm
A trading firm is a business entity that buys and sells financial instruments, commodities, or goods—often using market analysis, risk management, and capital allocation strategies—to generate profit from price differences and market movements.
-
D.
fictional retail establishment
A fictional retail establishment is an imagined store or shop, often created in literature, film, or games, that sells goods or services within a constructed world or narrative setting.
-
E.
fictional research institution
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.
- 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_69f76e2d7e8c8190bac4e90734566799 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.