Triple
T38542933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Winnipeg Goldeyes |
E924882
|
entity |
| Predicate | usesLeagueRules |
P6601
|
FINISHED |
| Object | American Association rules |
—
|
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: American Association rules | Statement: [Winnipeg Goldeyes, usesLeagueRules, American Association rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLeagueRules Context triple: [Winnipeg Goldeyes, usesLeagueRules, American Association rules]
-
A.
associatedLeagueRuleAdoption
Indicates that there is a connection between an entity and the specific league rule adoption that governs or influences it.
-
B.
usedInLeague
Indicates that an entity (such as a team, player, or item) participates or is employed within a particular league.
-
C.
playedUnderRulesOf
chosen
Indicates that an activity or game was conducted in accordance with a specified set of rules or regulations.
-
D.
hasRulebook
Indicates that one entity possesses, is governed by, or is associated with a specific rulebook.
-
E.
supportsLeagueType
Indicates that one entity is compatible with, or designed to work with, a particular type or category of league.
- 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_69f76eadeac081909cdfdd0474cb6765 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcd2ec6ab88190b83ae99d390453f3 |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f81cbc8190b4fd3bfc3106c1f3 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:32 p.m.