Triple
T22104851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indiawin Sports |
E546258
|
entity |
| Predicate | competitionLevelManaged |
P101309
|
FINISHED |
| Object | professional T20 cricket |
—
|
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: professional T20 cricket | Statement: [Indiawin Sports, competitionLevelManaged, professional T20 cricket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competitionLevelManaged Context triple: [Indiawin Sports, competitionLevelManaged, professional T20 cricket]
-
A.
leagueLevelManaged
Indicates that an entity is responsible for managing or overseeing a particular competitive league level.
-
B.
competitionLevelOf
Indicates the degree or intensity of competitiveness associated with an entity, event, or context.
-
C.
competitionLevel
Indicates the degree or intensity of competitive pressure or rivalry present in a given context or interaction.
-
D.
levelOfCompetitionAdministered
chosen
Indicates the specific competitive tier or intensity at which an activity, event, or process is formally managed or overseen.
-
E.
managedInLeague
Indicates that an entity served as a manager or head coach for a team participating in a specified league.
- 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_69e11e378dc08190896d6a51597afd5a |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1291815f88190a6eaf73e444dc1c2 |
completed | April 28, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69e71b20ec50819096ac196c798f8e3c |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:30 p.m.