Triple
T1441115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mountain West Conference men's basketball |
E31073
|
entity |
| Predicate | determinesChampionBy |
P29352
|
FINISHED |
| Object | regular season standings |
—
|
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: regular season standings | Statement: [Mountain West Conference men's basketball, determinesChampionBy, regular season standings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: determinesChampionBy Context triple: [Mountain West Conference men's basketball, determinesChampionBy, regular season standings]
-
A.
decidingGameWinner
Indicates that an event, action, or process determines which participant is the winner of a game.
-
B.
mainWinner
Indicates that one entity is the primary or overall winner in a competition, contest, or comparative outcome relative to others.
-
C.
champion
Indicates that one entity has won a competition or contest and holds the top position or title over others.
-
D.
championedBy
Indicates that an entity is actively supported, promoted, or advocated for by another entity.
-
E.
wonBy
Indicates that a contest, game, or competition is decided in favor of a particular participant or side.
- 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_69a4991633388190a4d61b5a98aa407a |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c5ff8dbc81909eafcfc9f2260a22 |
completed | March 1, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69a4c478f65481909ee716791c663491 |
completed | March 1, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69a4c5fd2c5c81909283b7a74aff89b7 |
completed | March 1, 2026, 11:04 p.m. |
Created at: March 1, 2026, 8 p.m.