Triple
T24647810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2024 ICC Men's T20 World Cup |
E610163
|
entity |
| Predicate | selectionOfTeamsBy |
P85421
|
FINISHED |
| Object | ICC regional qualifiers |
—
|
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: ICC regional qualifiers | Statement: [2024 ICC Men's T20 World Cup, selectionOfTeamsBy, ICC regional qualifiers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selectionOfTeamsBy Context triple: [2024 ICC Men's T20 World Cup, selectionOfTeamsBy, ICC regional qualifiers]
-
A.
teamSelection
Indicates the assignment or choice of one or more individuals or entities to be part of a specific team.
-
B.
eligibleTeamsFrom
chosen
Indicates that certain teams qualify or are allowed to originate from a specified source, context, or selection criteria.
-
C.
squadSelectionBasis
Indicates the criterion or rationale used to choose which individuals are included in a particular squad or team.
-
D.
selectionMadeBy
Indicates that a particular choice or selection was performed or decided by a specific agent or entity.
-
E.
primaryTeams
Indicates that one or more teams are the main or principal teams associated with a given 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_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.