Triple
T14173140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knight Riders |
E351260
|
entity |
| Predicate | featuresSportOrActivity |
P67409
|
FINISHED |
| Object | motorcycle jousting |
—
|
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: motorcycle jousting | Statement: [Knight Riders, featuresSportOrActivity, motorcycle jousting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresSportOrActivity Context triple: [Knight Riders, featuresSportOrActivity, motorcycle jousting]
-
A.
sportFocus
Indicates that one entity has a primary emphasis, specialization, or concentration on a particular sport represented by the other entity.
-
B.
sportEventType
Indicates the specific kind or category of sport associated with a given sporting event.
-
C.
sportCategory
Indicates that one entity is classified as a type or category of sport to which the other entity (typically a specific sport or sporting event) belongs.
-
D.
relatedSport
chosen
Indicates that there is an association or connection between an entity and a particular sport.
-
E.
sportsAndRecreation
Indicates a relationship where an entity is associated with, involved in, or designated for sports or recreational activities.
- 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_69d8278834a08190b0f1784e58d7b99c |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61b5dcbc8190b0cfcce5e6c6d582 |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05baed64819096590e5618a3a8ed |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:01 a.m.