Triple
T8996140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roy McGivern |
E214917
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | association football official |
C7075
|
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: association football official Context triple: [Roy McGivern, instanceOf, association football official]
-
A.
association football referee
chosen
An association football referee is the official responsible for enforcing the Laws of the Game on the field, making decisions on play, fouls, and disciplinary actions to ensure a fair and safe match.
-
B.
association football organization
An association football organization is an entity that governs, manages, or coordinates the playing, administration, and development of soccer competitions, clubs, and related activities within a defined scope or jurisdiction.
-
C.
association football defender
An association football defender is a player whose primary role is to prevent the opposing team from creating and converting goal-scoring opportunities, typically by marking attackers, intercepting passes, and blocking shots near their own goal.
-
D.
association football league system
An association football league system is a hierarchical structure of interconnected football leagues, typically organized by promotion and relegation, that determines the competitive levels and progression of clubs within a country or region.
-
E.
association football manager
An association football manager is the individual responsible for leading a football team by planning tactics, selecting players, overseeing training, and making strategic decisions before and during matches.
- 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_69ca83a05c608190bdfdbdb25e994b39 |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 7:04 p.m.