Triple
T32465685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Denver–Colorado College rivalry |
E829696
|
entity |
| Predicate | isRivalryForTeam |
P101805
|
FINISHED |
| Object | Denver Pioneers men's ice hockey |
—
|
NE NERFINISHED |
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: Denver Pioneers men's ice hockey | Statement: [Denver–Colorado College rivalry, isRivalryForTeam, Denver Pioneers men's ice hockey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRivalryForTeam Context triple: [Denver–Colorado College rivalry, isRivalryForTeam, Denver Pioneers men's ice hockey]
-
A.
isPartOfRivalry
chosen
Indicates that one entity participates as a member or component in an ongoing rivalry involving another entity.
-
B.
hasRivalryAspect
Indicates that there exists a competitive or adversarial relationship or dimension between entities.
-
C.
hasRivalryContext
Indicates that there exists a competitive or adversarial relationship between entities within a specific situational or contextual framework.
-
D.
hasRivalryRoot
Indicates that a rivalry relationship originates from, or is fundamentally based on, a particular source, cause, or underlying factor.
-
E.
rivalTeam
Indicates that one team is in a competitive or adversarial relationship with another team, often vying for superiority or dominance.
- 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_69f6c351255c81908e24cede60032639 |
completed | May 3, 2026, 3:38 a.m. |
| PD | Predicate disambiguation | batch_69f6ba700a708190ab6db62791e43774 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:57 a.m.