Triple
T10910469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICC Cricket World Cup Qualifier 2018 matches |
E257684
|
entity |
| Predicate | qualifiedTeamsCount |
P96366
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [ICC Cricket World Cup Qualifier 2018 matches, qualifiedTeamsCount, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: qualifiedTeamsCount Context triple: [ICC Cricket World Cup Qualifier 2018 matches, qualifiedTeamsCount, 2]
-
A.
qualifiedTeam
Indicates that a team has met the necessary criteria or achieved the required results to advance or be accepted into a particular stage, event, or competition.
-
B.
numberOfParticipatingTeamsInQualifying
Indicates the total number of teams that take part in the qualifying stage of a competition or event.
-
C.
hasNumberOfTeams
Indicates the quantity of teams associated with or contained by a given entity.
-
D.
teamCountType
Indicates how the number of teams is categorized or measured within a given context.
-
E.
eligibleTeamsFrom
Indicates that certain teams qualify or are allowed to originate from a specified source, context, or selection criteria.
- F. None of above. chosen
Provenance (4 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_69d6aa864ed88190818280ab6791d065 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d77071492c8190bd6f8623a59464c9 |
completed | April 9, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69d70d3f9dc88190a686a8b0dd6a3b21 |
completed | April 9, 2026, 2:21 a.m. |
| PDg | Predicate description generation | batch_69d710400ea88190ac2ed6f0a13d62c1 |
completed | April 9, 2026, 2:34 a.m. |
Created at: April 8, 2026, 9:22 p.m.