Triple
T22074367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irani Cup |
E545485
|
entity |
| Predicate | selectionBasisForRestOfIndia |
P146525
|
FINISHED |
| Object | top performers from Indian domestic cricket |
—
|
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: top performers from Indian domestic cricket | Statement: [Irani Cup, selectionBasisForRestOfIndia, top performers from Indian domestic cricket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selectionBasisForRestOfIndia Context triple: [Irani Cup, selectionBasisForRestOfIndia, top performers from Indian domestic cricket]
-
A.
stateInIndia
Indicates that a given state is located within the country of India.
-
B.
areaRankInIndia
Indicates the relative position of an entity when all entities in India are ordered by their area size.
-
C.
includesIndianStateOrTerritory
Indicates that one entity encompasses, contains, or covers the area of an Indian state or union territory.
-
D.
rankByPopulationInIndia
Indicates the relative ordering of entities based on their population size within India.
-
E.
rankByLengthInIndia
Indicates an ordering of items based on their length specifically within the context or boundaries of India.
- 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_69e11e344dfc81909b1d88a7221329c7 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1288affb081908b64742f7bf467fa |
completed | April 28, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69e6f64a6a70819089d1a6c3a2384861 |
completed | April 21, 2026, 4 a.m. |
| PDg | Predicate description generation | batch_69e6fad59ef48190b62a2af636918a15 |
completed | April 21, 2026, 4:19 a.m. |
Created at: April 16, 2026, 8:28 p.m.