Triple
T22916309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Confederação Brasileira de Jiu-Jitsu |
E568741
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Brazilian organization |
C18926
|
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: Brazilian organization Context triple: [Confederação Brasileira de Jiu-Jitsu, instanceOf, Brazilian organization]
-
A.
Portuguese organization
A Portuguese organization is an entity based in Portugal, such as a company, association, or institution, that is formally structured to pursue specific economic, social, cultural, or public-interest objectives within the framework of Portuguese law.
-
B.
Argentine organization
An Argentine organization is any formally or informally structured group based in Argentina that coordinates people and resources to pursue shared goals, such as business, social, cultural, or political objectives.
-
C.
Brazilian company
A Brazilian company is a legally recognized business entity established and operating under Brazil’s corporate laws, regulations, and tax system, conducting commercial, industrial, or service activities within or from Brazil.
-
D.
South American organization
chosen
A South American organization is an entity based in or primarily serving South America that coordinates people, resources, and activities to pursue shared regional, social, economic, cultural, or political objectives.
-
E.
Peruvian organization
A Peruvian organization is a formally structured group or entity established in Peru to pursue specific economic, social, cultural, political, or charitable objectives within the framework of Peruvian law.
- 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_69e2458d90c88190a58cead4e781ca6a |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:42 p.m.