Triple
T18739450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICC T20I Team Rankings |
E458251
|
entity |
| Predicate | hasRankingLevel |
P34581
|
FINISHED |
| Object | number 1 ranked T20I team |
—
|
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: number 1 ranked T20I team | Statement: [ICC T20I Team Rankings, hasRankingLevel, number 1 ranked T20I team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRankingLevel Context triple: [ICC T20I Team Rankings, hasRankingLevel, number 1 ranked T20I team]
-
A.
hasRankingCategory
Indicates that an entity is associated with a particular ranking category or tier within an ordered classification system.
-
B.
hasRankingUnit
Indicates that one entity is associated with a specific unit or scale used to express its ranking or ordered position.
-
C.
hasRankLevels
chosen
Indicates that an entity is associated with one or more hierarchical rank levels within a ranking or grading system.
-
D.
hasRankingFactor
Indicates that one entity contributes as a factor to determining the ranking or ordered position of another entity.
-
E.
hasRankingStrength
Indicates the relative strength or priority of an entity’s ranking compared to others in a given ordering or evaluation.
- 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_69d8d394dc308190b6725073f5db324c |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5768ca990819098102f8522ce401f |
completed | April 20, 2026, 12:42 a.m. |
| PD | Predicate disambiguation | batch_69e48d03766c8190a43f7681842f4f8d |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:51 a.m.