Triple
T21456897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICC World Test Championship |
E529364
|
entity |
| Predicate | thirdCycle |
P144419
|
FINISHED |
| Object | 2023–2025 |
—
|
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: 2023–2025 | Statement: [ICC World Test Championship, thirdCycle, 2023–2025]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thirdCycle Context triple: [ICC World Test Championship, thirdCycle, 2023–2025]
-
A.
thirdTier
Indicates that an entity occupies a third level or rank within a hierarchical structure or classification.
-
B.
thirdStageType
Indicates the specific kind or classification of a third stage within a multi-stage process or structure.
-
C.
thirdSingle
Indicates that an entity is the third single (e.g., third single release) associated with another entity, typically in a sequence such as from an album or artist.
-
D.
thirdMovementType
Indicates the specific type or category of the third movement within a larger sequence or structure of movements.
-
E.
thirdGeneration
Indicates that one entity is the grandchild (third generation) relative to another entity in a lineage or succession.
- 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_69e0c458133481908ae8b41a12c4edec |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9e9d7af248190a3bc06a390f390bf |
completed | April 23, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69e631df1b38819088d3604854e697b4 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e63d2aca38819094d312078feaa436 |
completed | April 20, 2026, 2:50 p.m. |
Created at: April 16, 2026, 6:08 p.m.