Triple
T7120863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2016 ICC World Twenty20 |
E165945
|
entity |
| Predicate | super10Groups |
P61730
|
FINISHED |
| Object | Group 1 |
—
|
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: Group 1 | Statement: [2016 ICC World Twenty20, super10Groups, Group 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: super10Groups Context triple: [2016 ICC World Twenty20, super10Groups, Group 1]
-
A.
topTeam
Indicates that the referenced team is ranked as the best or leading team within a given group, competition, or context.
-
B.
coveredGroup
Indicates that one group or set is included within, or has its members protected or accounted for by, another group or arrangement.
-
C.
participantGroup
chosen
Indicates a relationship in which a set or group of entities jointly participate in a common event, activity, or interaction.
-
D.
superSixStage
Indicates that an entity is in or associated with a sixth and particularly advanced or superior stage within a defined multi-stage process or progression.
-
E.
typicalGroup
Indicates that the subject belongs to or represents a standard, characteristic, or commonly occurring group associated with the object.
- 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_69c6888227bc8190a1394679e3116f90 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e61e67788190959fbd7fa6c929d3 |
completed | March 27, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c7289881909f3b533c384f9ed4 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:43 p.m.