Triple
T32465665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Denver–Colorado College rivalry |
E829696
|
entity |
| Predicate | isIntraStateRivalry |
P107240
|
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, isIntraStateRivalry, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isIntraStateRivalry Context triple: [Denver–Colorado College rivalry, isIntraStateRivalry, true]
-
A.
isIntraStateRivalryOf
chosen
Indicates that there is a rivalry occurring within the same state or internal political unit between the related entities.
-
B.
hasInStateRivalries
Indicates that two entities are rivals or competitors within the same state or internal jurisdiction.
-
C.
hasRivalState
Indicates that one state maintains a rivalry or competitive opposition with another state.
-
D.
hasRivalryAspect
Indicates that there exists a competitive or adversarial relationship or dimension between entities.
-
E.
hasLocalRivalry
Indicates that there is an ongoing competitive or adversarial relationship between entities that are geographically close or share the same local area.
- 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_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:57 a.m.