Triple
T32465667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Denver–Colorado College rivalry |
E829696
|
entity |
| Predicate | featuresConferenceGames |
P123796
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Denver–Colorado College rivalry, featuresConferenceGames, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresConferenceGames Context triple: [Denver–Colorado College rivalry, featuresConferenceGames, true]
-
A.
includesGamesFromConference
chosen
Indicates that something contains or incorporates games that originate from a specified conference.
-
B.
playsConference
Indicates that an entity (typically a team or player) participates in or is a member of a specific conference.
-
C.
featuredConferenceOfChampion
Indicates that a conference is the primary or highlighted event associated with a particular champion.
-
D.
gamesOf
Indicates a relationship where one entity is the set, list, or collection of games associated with another entity.
-
E.
competitionConference
Indicates that a competition is associated with, held at, or organized as part of a particular conference.
- 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_69f3491ee87c81908cbf5890079c2af6 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a0117b6539c8190be7d231e891fe546 |
completed | May 10, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_6a011762f7ec8190afc884b92419d33f |
completed | May 10, 2026, 11:40 p.m. |
Created at: May 1, 2026, 12:57 a.m.