Triple
T37379659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Aquatics Championships |
E928394
|
entity |
| Predicate | includesRelayEvents |
—
|
GENERATED |
| Object | yes |
—
|
UNRECOGNIZED GENERATED |
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesRelayEvents Context triple: [European Aquatics Championships, includesRelayEvents, yes]
-
A.
isRelayEvent
Indicates that an event functions as an intermediary or forwarding step within a larger process or communication chain.
-
B.
includesEvents
Indicates that one entity contains or encompasses one or more events as part of its scope or composition.
-
C.
relayEvents
Indicates that one entity forwards or passes along events it receives to another entity or system.
-
D.
usesRelaySatellite
Indicates that one entity communicates or transmits data indirectly by routing it through a relay satellite rather than via a direct link.
-
E.
coversEventsAfter
Indicates that one event or time interval extends to include all events occurring after a specified reference event or time.
- F. None of above. chosen
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_69f76eb9e66881908534cf22d04c3b5a |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:16 p.m.