Triple
T26721079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quaid-e-Azam Trophy |
E673701
|
entity |
| Predicate | cricketCategory |
P146528
|
FINISHED |
| Object | long-format 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: long-format cricket | Statement: [Quaid-e-Azam Trophy, cricketCategory, long-format cricket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cricketCategory Context triple: [Quaid-e-Azam Trophy, cricketCategory, long-format 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.
partOfCricketStructure
Indicates that one entity is a component or constituent part of a larger cricket-related structure or facility.
-
E.
sportsCategory
Indicates that one entity is classified as a type or category within the domain of sports to which the other entity belongs.
- 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_69eecda481d08190aea69f2f7c745f56 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f61801feb88190b24aca1c52167679 |
completed | May 2, 2026, 3:28 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:40 a.m.