Triple
T21136193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kansas–Missouri rivalry |
E520821
|
entity |
| Predicate | featuresAnnualGamesHistoricallyIn |
P130901
|
FINISHED |
| Object | basketball |
—
|
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: basketball | Statement: [Kansas–Missouri rivalry, featuresAnnualGamesHistoricallyIn, basketball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresAnnualGamesHistoricallyIn Context triple: [Kansas–Missouri rivalry, featuresAnnualGamesHistoricallyIn, basketball]
-
A.
annualGameName
Indicates that the predicate specifies the name of a game as it is designated for a particular year or annual edition.
-
B.
gamesHeldEvery
Indicates that games are conducted with a regular frequency or on every occurrence of a specified time interval or condition.
-
C.
gamesOf
chosen
Indicates a relationship where one entity is the set, list, or collection of games associated with another entity.
-
D.
homeGamesPlayedBy
Indicates the number or set of home games that are played by a particular team or player.
-
E.
originalGamesYear
Indicates the year in which the original version of the game was first released.
- 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_69e0b50b53048190ae34e8abbe3c5ada |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7235aae588190bf9f7b40553bfa0e |
completed | April 21, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69e5f5ed6c8c8190b31092a5d4c3de5d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:57 p.m.