Triple
T26892596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Rajshahi |
E677814
|
entity |
| Predicate | hasCricketVenue |
P12425
|
FINISHED |
| Object | Rajshahi District Stadium |
—
|
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: Rajshahi District Stadium | Statement: [City of Rajshahi, hasCricketVenue, Rajshahi District Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCricketVenue Context triple: [City of Rajshahi, hasCricketVenue, Rajshahi District Stadium]
-
A.
hasCricketGround
chosen
Indicates that one entity possesses, contains, or includes a cricket ground as part of its facilities or attributes.
-
B.
domesticCricketLocation
Indicates the location where a domestic cricket match, competition, or related event takes place.
-
C.
cricketGroundUsedBy
Indicates that a particular cricket ground is regularly used by a specified team, club, or organization for playing or practicing cricket.
-
D.
hasSportsGround
Indicates that an entity possesses, includes, or is associated with a sports ground or athletic field as part of its facilities or area.
-
E.
servesCricketGround
Indicates that one entity functions as the home or host venue for cricket matches or activities for another entity.
- 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_69eee9befee48190a26f214faa867be7 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 27, 2026, 5:46 a.m.