Triple
T19547795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mohali |
E489119
|
entity |
| Predicate | cricketStadiumUse |
P95893
|
FINISHED |
| Object | international cricket matches |
—
|
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: international cricket matches | Statement: [Mohali, cricketStadiumUse, international cricket matches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cricketStadiumUse Context triple: [Mohali, cricketStadiumUse, international cricket matches]
-
A.
cricketGroundUsedBy
Indicates that a particular cricket ground is regularly used by a specified team, club, or organization for playing or practicing cricket.
-
B.
hasStadiumUse
Indicates that one entity (typically a team, organization, or event) uses or is authorized to use a particular stadium for its activities or purposes.
-
C.
cricketGroundHosts
Indicates that a particular cricket ground serves as the venue for hosting a specified cricket match, team, or event.
-
D.
stadiumUsedFor
chosen
Indicates that a particular stadium is used for a specific activity, event, or purpose.
-
E.
partOfCricketStructure
Indicates that one entity is a component or constituent part of a larger cricket-related structure or facility.
- 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_69d8e8db5b6c8190984b61f91981f575 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63d2d8a6081908e9bb3a6f5d85896 |
completed | April 20, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69e514d4df3c8190b7e9b3b4fdf9452a |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:41 p.m.