Triple
T32465611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Dakota–Denver rivalry |
E829695
|
entity |
| Predicate | typicalImplication |
—
|
GENERATED |
| Object | national rankings |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalImplication Context triple: [North Dakota–Denver rivalry, typicalImplication, national rankings]
-
A.
hasImplicationsFor
chosen
Indicates that one entity’s state, action, or condition leads to consequences, effects, or relevance for another entity.
-
B.
typicalAssumption
Indicates that something is taken as a standard or default assumption that generally holds in typical or normal circumstances.
-
C.
typicalCircumstance
Indicates the usual or commonly occurring situation, condition, or context in which an event, action, or relationship typically takes place.
-
D.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
E.
policyImplication
Indicates that one policy, decision, or condition leads to, justifies, or necessitates another policy outcome or course of action.
- F. None of above.
Provenance (1 batch)
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. |
Created at: May 1, 2026, 12:57 a.m.