Triple
T32465611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Dakota–Denver rivalry |
E829695
|
entity |
| Predicate | typicalImplication |
P94557
|
FINISHED |
| Object | national rankings |
—
|
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: national rankings | Statement: [North Dakota–Denver rivalry, typicalImplication, national rankings]
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 (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_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:57 a.m.