Triple
T3768329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amaury Sport Organisation |
E82734
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | sports event organizer |
C11728
|
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: sports event organizer Context triple: [Amaury Sport Organisation, instanceOf, sports event organizer]
-
A.
event producer
An event producer is an entity responsible for creating, organizing, and managing events by coordinating resources, logistics, and stakeholders to deliver a planned experience.
-
B.
Olympic Games organizer
An Olympic Games organizer is responsible for planning, coordinating, and managing all aspects of hosting the Olympic Games, including logistics, venues, athletes, security, ceremonies, and compliance with International Olympic Committee regulations.
-
C.
professional golf tour organizer
chosen
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.
-
D.
multi-sport event
A multi-sport event is a large-scale organized competition in which athletes from various regions or groups compete across multiple different sports within a unified program and schedule.
-
E.
sports administration organization
A sports administration organization is an entity responsible for governing, regulating, and managing the operations, policies, and development of sports activities, leagues, or associations within its jurisdiction.
- 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_69ad8b207b0081909d2b48843fbd8795 |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3:35 p.m.