Triple
T24647791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2024 ICC Men's T20 World Cup |
E610163
|
entity |
| Predicate | qualifiedAsHost |
P156905
|
FINISHED |
| Object | West Indies |
—
|
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: West Indies | Statement: [2024 ICC Men's T20 World Cup, qualifiedAsHost, West Indies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: qualifiedAsHost Context triple: [2024 ICC Men's T20 World Cup, qualifiedAsHost, West Indies]
-
A.
qualifiedAsHost
chosen
Indicates that an entity has met the necessary criteria or standards to serve in the role of a host.
-
B.
mayBeHostedBy
Indicates that an entity has the possibility or option of being hosted or accommodated by another entity.
-
C.
mayHost
Indicates that an entity is permitted or able to serve as the location or organizer for another entity or event.
-
D.
qualificationMethodOfHost
Indicates the method or process by which a host qualifies or is determined to be eligible for a particular role, status, or participation.
-
E.
supportsHostType
Indicates that one entity is capable of operating with, accommodating, or being compatible with a specified host type.
- 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_69e2c4d350a481909170482bc2ce6af9 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f422aee0408190899efe7e24ef2b40 |
completed | May 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f420e92cc88190a803aecdae78a051 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 2:33 a.m.