Triple
T36476923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gamblers |
E898692
|
entity |
| Predicate | leagueChampionshipName |
P130817
|
FINISHED |
| Object | Clark Cup |
E577559
|
NE 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: Clark Cup | Statement: [Gamblers, leagueChampionshipName, Clark Cup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leagueChampionshipName Context triple: [Gamblers, leagueChampionshipName, Clark Cup]
-
A.
championshipLeague
Indicates that an entity is a championship-level competition or league in which teams or individuals compete for a title.
-
B.
leagueChampionshipContext
chosen
Indicates the relationship between a sports league and the championship context in which a particular event, season, or achievement occurs (e.g., which league’s championship is being referred to).
-
C.
championLeague
Indicates that an entity has won or holds the championship title in a particular league or competitive event.
-
D.
leagueChampionships
Indicates the number of league championship titles an entity has won.
-
E.
leagueCup
Indicates that an entity is a cup-style competition organized within or by a specific league.
- F. None of above.
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_69f76e5a0e088190a2b6706aeb41723c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3a20b31b3081908d9e34ad87727732 |
completed | June 23, 2026, 5:59 a.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:10 p.m.