Triple
T1436273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eden Gardens |
E30567
|
entity |
| Predicate | hostedMatch |
P527
|
FINISHED |
| Object | 2016 ICC World Twenty20 final |
—
|
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: 2016 ICC World Twenty20 final | Statement: [Eden Gardens, hostedMatch, 2016 ICC World Twenty20 final]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostedMatch Context triple: [Eden Gardens, hostedMatch, 2016 ICC World Twenty20 final]
-
A.
sportsEventHosted
chosen
Indicates that a particular sports event was organized, arranged, or held by a specified host entity (such as a venue, organization, or city).
-
B.
leagueLevelHosted
Indicates the competitive tier or division level at which an event, match, or competition is hosted within a league structure.
-
C.
hosted
Indicates that one entity organized and provided the venue or platform for an event, activity, or presence involving another entity.
-
D.
hostsLeague
Indicates that one entity serves as the organizing or venue-providing host for a particular league.
-
E.
openingMatch
Indicates that one entity serves as the initial or first match, game, or contest in a series, event, or competition involving 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_69a498fc69ec8190b61722bd4b67c4d2 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c5ff8dbc81909eafcfc9f2260a22 |
completed | March 1, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69a4c478f65481909ee716791c663491 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.