Triple
T26209471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cricket |
E655443
|
entity |
| Predicate | hasMajorDomesticLeague |
P191668
|
FINISHED |
| Object | Indian Premier League |
—
|
NE NERFINISHED |
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: Indian Premier League | Statement: [Cricket, hasMajorDomesticLeague, Indian Premier League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorDomesticLeague Context triple: [Cricket, hasMajorDomesticLeague, Indian Premier League]
-
A.
isMajorProfessionalLeagueIn
Indicates that a professional sports league is recognized as a major league within a specified country or region.
-
B.
hasMajorSport
Indicates that an entity is associated with or participates in a primary or most prominent sport.
-
C.
associatedMajorLeague
Indicates a relationship where one entity is linked or connected to a specific Major League organization or team.
-
D.
hasHomeCountryLeague
Indicates that an entity (typically a sports team or player) is associated with a specific league that operates in its home country.
-
E.
domesticLeagueTitle
Indicates that an entity has won a championship title in its primary national (domestic) league competition.
- 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_69ee5b49adb4819086545280d4ef6337 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
| PDg | Predicate description generation | batch_69fce76669408190b1beef8899a8a5e2 |
completed | May 7, 2026, 7:26 p.m. |
Created at: April 26, 2026, 8:52 p.m.