Triple
T22271671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Utah Utes men's basketball |
E550492
|
entity |
| Predicate | hasInStateRivalries |
P147645
|
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: [Utah Utes men's basketball, hasInStateRivalries, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInStateRivalries Context triple: [Utah Utes men's basketball, hasInStateRivalries, true]
-
A.
hasRivalryContext
Indicates that there exists a competitive or adversarial relationship between entities within a specific situational or contextual framework.
-
B.
hasRivalryAspect
Indicates that there exists a competitive or adversarial relationship or dimension between entities.
-
C.
hasRivalryRoot
Indicates that a rivalry relationship originates from, or is fundamentally based on, a particular source, cause, or underlying factor.
-
D.
hasRivalryCategory
Indicates that there exists a competitive or adversarial relationship between entities that falls into a specific classified type or category of rivalry.
-
E.
hasRivalryFormat
Indicates that there is a specific structure, set of rules, or format that defines how a rivalry between entities is conducted or organized.
- F. None of above. chosen
Provenance (4 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_69e11e43d8208190aff4f9cf7f2c2a8a |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f141c056cc819088dae6f2b9a1d526 |
completed | April 28, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e7342ce08c8190bc0a7085f4a952e7 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:40 p.m.