Triple
T20111091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VTB United League |
E490330
|
entity |
| Predicate | topTierLeagueOf |
P7559
|
FINISHED |
| Object | Russian basketball league system |
—
|
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: Russian basketball league system | Statement: [VTB United League, topTierLeagueOf, Russian basketball league system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topTierLeagueOf Context triple: [VTB United League, topTierLeagueOf, Russian basketball league system]
-
A.
leagueType
Indicates the classification or category of a league within a broader organizational or competitive structure.
-
B.
aboveLeague
Indicates that one entity is in a higher league, tier, or competitive level than another.
-
C.
isTopLevelLeagueIn
chosen
Indicates that a sports league is the highest (top-tier) competitive level within a specified country or region.
-
D.
stateLeague
Indicates that a sports team or club competes in, or is affiliated with, a particular state-level league or competition.
-
E.
competitiveLeague
Indicates that the entities participate in the same organized competition or league where they compete against each other.
- 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_69da62636cc08190982cc71733a17b8d |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e666e0180c8190adeead0e60a099b0 |
completed | April 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69e54cf788188190a46cc49c9ce7617f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:29 p.m.