Triple
T25293112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martin Guptill |
E634142
|
entity |
| Predicate | hasPlayedInT20League |
P162090
|
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: [Martin Guptill, hasPlayedInT20League, Indian Premier League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlayedInT20League Context triple: [Martin Guptill, hasPlayedInT20League, Indian Premier League]
-
A.
T20WorldCupAppearances
Indicates the number of times an entity has participated in T20 Cricket World Cup tournaments.
-
B.
hasPlayedDomesticCricketFor
Indicates that a person has been a member of and played domestic-level cricket matches for a specified team or organization.
-
C.
t20WorldCupParticipation
Indicates that an entity took part as a team or player in a T20 Cricket World Cup tournament.
-
D.
T20Franchise
Indicates that an entity is a professional cricket team participating in a Twenty20 (T20) franchise-based league.
-
E.
playedForIPLTeam
Indicates that one entity has been a player representing the specified IPL (Indian Premier League) team.
- 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_69e75a9503d48190b80a005c6af0cb50 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f622abdfac8190988421c946411d7e |
completed | May 2, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69f620dc38088190b56b2b15ed75b3c2 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f621fbfc2c8190bfa802d7dc0f6aa4 |
completed | May 2, 2026, 4:10 p.m. |
Created at: April 21, 2026, 1:22 p.m.