Triple
T22074993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | India A cricket team |
E545499
|
entity |
| Predicate | playsSeriesType |
P29019
|
FINISHED |
| Object | unofficial Test series |
—
|
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: unofficial Test series | Statement: [India A cricket team, playsSeriesType, unofficial Test series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsSeriesType Context triple: [India A cricket team, playsSeriesType, unofficial Test series]
-
A.
playType
chosen
Indicates the specific category or style of play or performance associated with an event or action.
-
B.
launchesSeries
Indicates that one entity initiates or starts a sequence or series of related events, actions, or items involving another entity.
-
C.
playsSeasonSeries
Indicates that an entity participates as a competitor or team in a particular season of a series or league.
-
D.
seriesOf
Indicates that one entity is a sequence or ordered set of related items, events, or parts that collectively form or belong to another entity.
-
E.
inSeriesFormat
Indicates that one entity is organized or presented as part of a sequential series format relative to another 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_69e11e344dfc81909b1d88a7221329c7 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128b1904881909a1769ce8be39e05 |
completed | April 28, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69e6f64a6a70819089d1a6c3a2384861 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:28 p.m.