Triple
T18220478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IYS Insurance |
E436288
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional insurance company |
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 insurance company Context triple: [IYS Insurance, instanceOf, fictional insurance company]
-
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 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.
-
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 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.
-
E.
fictional hotel
A fictional hotel is an imagined lodging establishment, often richly detailed in setting, atmosphere, and services, that serves as a narrative backdrop or central location in stories, films, games, or other creative works.
- 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_69d8b9103a8081908bbb0836fef10efd |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:32 a.m.