Triple
T26924621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESL |
E677744
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tournament organizer |
C6712
|
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: tournament organizer Context triple: [ESL, instanceOf, tournament organizer]
-
A.
race organizer
A race organizer is an entity responsible for planning, coordinating, and managing all logistical, regulatory, and participant-related aspects of a race event.
-
B.
motorsport organizer
A motorsport organizer is an entity responsible for planning, coordinating, and overseeing competitive racing events, ensuring regulatory compliance, safety, logistics, and participant management.
-
C.
event producer
chosen
An event producer is an entity responsible for creating, organizing, and managing events by coordinating resources, logistics, and stakeholders to deliver a planned experience.
-
D.
festival organization
Festival organization is the coordinated planning, management, and execution of all logistical, financial, promotional, and experiential aspects required to design and deliver a successful festival event.
-
E.
professional golf tour organizer
A professional golf tour organizer is responsible for planning, coordinating, and managing all aspects of professional golf tournaments and tours, including scheduling events, securing venues and sponsors, handling player logistics, and ensuring compliance with governing bodies and regulations.
- 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_69eee9bdebc48190ba90a12a63e09c73 |
completed | April 27, 2026, 4:44 a.m. |
Created at: April 27, 2026, 6:09 a.m.