Triple
T27147586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abu Nechim |
E681991
|
entity |
| Predicate | domesticCricketFormat |
P146528
|
FINISHED |
| Object | first-class 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: first-class cricket | Statement: [Abu Nechim, domesticCricketFormat, first-class cricket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: domesticCricketFormat Context triple: [Abu Nechim, domesticCricketFormat, first-class cricket]
-
A.
typeOfCricket
chosen
Indicates that one entity is a specific kind or category of cricket in relation to another entity.
-
B.
domesticCricketCountry
Indicates that one entity is a country in which the other entity participates in or is associated with domestic cricket competitions.
-
C.
hasPlayedDomesticCricketFor
Indicates that a person has been a member of and played domestic-level cricket matches for a specified team or organization.
-
D.
usesLimitedOversRules
Indicates that the action or event is conducted under limited-overs rules, typically involving a fixed maximum number of overs per side.
-
E.
domesticCricketLocation
Indicates the location where a domestic cricket match, competition, or related event takes place.
- 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_69eefacca3888190b67238d380e8f28b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 9:12 a.m.