Triple
T20291389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slovene National Benefit Society |
E510033
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Slovene-American organization |
C43233
|
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: Slovene-American organization Context triple: [Slovene National Benefit Society, instanceOf, Slovene-American organization]
-
A.
Slovak organization
A Slovak organization is an entity legally established or operating in Slovakia, such as a company, institution, association, or non-profit, that pursues specific economic, social, cultural, or public-interest objectives within the Slovak legal and regulatory framework.
-
B.
Serbian organization
A Serbian organization is a structured group or entity based in Serbia that coordinates people and resources to pursue specific social, economic, cultural, political, or charitable objectives within the Serbian context.
-
C.
Sorbian organization
A Sorbian organization is an entity dedicated to preserving, promoting, and representing the culture, language, and interests of the Sorbian minority community.
-
D.
Polish diaspora organization
A Polish diaspora organization is a formal group that unites people of Polish origin or affinity living abroad to preserve Polish culture, support community needs, and maintain connections with Poland.
-
E.
Czech organization
A Czech organization is an entity based in the Czech Republic that is formally structured to pursue specific goals, activities, or services within legal, social, cultural, or economic frameworks.
- F. None of above. chosen
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_69e0b4c652388190b782cad965e5a098 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 11:12 a.m.