Triple
T22356141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duleep Trophy |
E552656
|
entity |
| Predicate | cricketClass |
P146528
|
FINISHED |
| Object | first-class |
—
|
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: first-class | Statement: [Duleep Trophy, cricketClass, first-class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cricketClass Context triple: [Duleep Trophy, cricketClass, first-class]
-
A.
typeOfCricket
chosen
Indicates that one entity is a specific kind or category of cricket in relation to another entity.
-
B.
positionInCricket
Indicates the specific fielding, batting, or bowling role or spot that an entity occupies within the game of cricket.
-
C.
partOfCricketStructure
Indicates that one entity is a component or constituent part of a larger cricket-related structure or facility.
-
D.
domesticCricketCountry
Indicates that one entity is a country in which the other entity participates in or is associated with domestic cricket competitions.
-
E.
traditionalCricketTeam
Indicates that an entity is a cricket team organized and composed according to customary or historically established rules and structures of the sport.
- 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_69e11e4a0ad08190a385b4d343cf6524 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f157cf94508190b0f2c63ddfecb813 |
completed | April 29, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69e7300c20088190a59e5bf9e70384f3 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:44 p.m.