Triple
T22105168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stumpy |
E546266
|
entity |
| Predicate | tournamentHostAssociation |
P104236
|
FINISHED |
| Object | 2011 Cricket World Cup co-host nations |
—
|
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: 2011 Cricket World Cup co-host nations | Statement: [Stumpy, tournamentHostAssociation, 2011 Cricket World Cup co-host nations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tournamentHostAssociation Context triple: [Stumpy, tournamentHostAssociation, 2011 Cricket World Cup co-host nations]
-
A.
tournamentHost
Indicates that one entity serves as the organizer or official host of a tournament involving the other entity.
-
B.
tournamentHostConfederation
Indicates the confederation that is responsible for organizing or hosting a given tournament.
-
C.
associatedWithEventHost
chosen
Indicates that an entity has a relationship or connection with the host of a particular event.
-
D.
sportsEventHosted
Indicates that a particular sports event was organized, arranged, or held by a specified host entity (such as a venue, organization, or city).
-
E.
holdsTournamentsIn
Indicates that an entity organizes or conducts tournaments at or within a specified location.
- 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_69e11e378dc08190896d6a51597afd5a |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12918d7a4819080283c287a253c9f |
completed | April 28, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69e71b20ec50819096ac196c798f8e3c |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:30 p.m.