Triple
T38409879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boekelo |
E901443
|
entity |
| Predicate | sportsDisciplineAtEvent |
P179726
|
FINISHED |
| Object | cross-country riding |
—
|
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: cross-country riding | Statement: [Boekelo, sportsDisciplineAtEvent, cross-country riding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sportsDisciplineAtEvent Context triple: [Boekelo, sportsDisciplineAtEvent, cross-country riding]
-
A.
inSportDiscipline
chosen
Indicates that an entity participates, competes, or is involved in a specific sport discipline or event.
-
B.
sportDisciplineScope
Indicates the specific sport discipline or category within which a given relationship, rule, or activity is defined or applies.
-
C.
sportEventType
Indicates the specific kind or category of sport associated with a given sporting event.
-
D.
sportEvent
Indicates a relationship where an entity is involved in, associated with, or characterizes a competitive or organized sporting event.
-
E.
sportingEventAssociatedWith
Indicates that there is a relevant connection or involvement between a sporting event and another entity (such as a person, team, organization, or place).
- 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_69f76e61e79c81908b787d83b46ab92b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.