Triple
T2446136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riley Cup |
E53597
|
entity |
| Predicate | usedByLeagueType |
P10472
|
FINISHED |
| Object | minor league |
—
|
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: minor league | Statement: [Riley Cup, usedByLeagueType, minor league]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByLeagueType Context triple: [Riley Cup, usedByLeagueType, minor league]
-
A.
usedInLeague
Indicates that an entity (such as a team, player, or item) participates or is employed within a particular league.
-
B.
usedByTeam
Indicates that something (such as a resource, tool, or method) is utilized or employed by a particular team.
-
C.
leagueType
chosen
Indicates the classification or category of a league within a broader organizational or competitive structure.
-
D.
associatedLeagueRuleAdoption
Indicates that there is a connection between an entity and the specific league rule adoption that governs or influences it.
-
E.
includesLeague
Indicates that an entity (such as a competition, organization, or system) contains or encompasses a specific league as one of its components.
- 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_69ab495d227c8190b26ae6548eeb1019 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcabf477081908512df63ac1a6414 |
completed | March 7, 2026, 6:50 a.m. |
| PD | Predicate disambiguation | batch_69abc5ad8e588190b97c4cd7cf575043 |
completed | March 7, 2026, 6:29 a.m. |
Created at: March 6, 2026, 9:43 p.m.