Triple
T26363005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Prix de Trois-Rivières |
E660256
|
entity |
| Predicate | hasSupportEvents |
P58905
|
FINISHED |
| Object | various support races |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: various support races | Statement: [Grand Prix de Trois-Rivières, hasSupportEvents, various support races]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSupportEvents Context triple: [Grand Prix de Trois-Rivières, hasSupportEvents, various support races]
-
A.
supportedEvent
Indicates that an entity is capable of recognizing, handling, or being associated with a particular type of event.
-
B.
supportsEventSeries
Indicates that an entity provides the necessary functionality or resources to host, manage, or accommodate a recurring series of related events.
-
C.
includesEvents
chosen
Indicates that one entity contains or encompasses one or more events as part of its scope or composition.
-
D.
hasCoSanctionedEventsWith
Indicates that two entities have jointly sanctioned or approved the same events.
-
E.
hasOccasionalEvent
Indicates that an event or activity occurs irregularly or infrequently in relation to a given entity or context.
- F. None of above.
Provenance (3 batches)
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_69ee8126d52c8190bc0b34337c2c9aa8 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 26, 2026, 10:53 p.m.