Triple
T24581421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2006 FIFA World Cup organizing committee in Germany |
E608259
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | national organizing committee |
C6550
|
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: national organizing committee Context triple: [2006 FIFA World Cup organizing committee in Germany, instanceOf, national organizing committee]
-
A.
organizational committee
chosen
An organizational committee is a structured group of individuals formally appointed within an organization to plan, coordinate, and oversee specific functions, projects, or decision-making processes.
-
B.
national association
A national association is an organized body that represents and coordinates the interests, standards, and activities of a specific profession, industry, or cause across an entire country.
-
C.
national student organization
A national student organization is a formally structured, student-led group that operates across multiple educational institutions within a country to represent student interests, coordinate activities, and provide shared resources and opportunities.
-
D.
National Olympic Committee
A National Olympic Committee is the organization recognized by the International Olympic Committee as responsible for developing, promoting, and overseeing Olympic sports and athletes within a specific country or territory.
-
E.
joint organization
A joint organization is a collaborative entity formed by two or more independent parties that share resources, responsibilities, and decision-making to achieve common 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_69e2c4ce89248190ad99e18f0638dfbb |
completed | April 17, 2026, 11:39 p.m. |
Created at: April 18, 2026, 2:29 a.m.