Triple
T22075271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alastair Cook |
E545505
|
entity |
| Predicate | ODIMatches |
P23205
|
FINISHED |
| Object | 92 |
—
|
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: 92 | Statement: [Alastair Cook, ODIMatches, 92]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ODIMatches Context triple: [Alastair Cook, ODIMatches, 92]
-
A.
firstODIMatchTeams
Indicates that the related entities are the teams that played in the first One Day International (ODI) match between them.
-
B.
firstODIMatchYear
Indicates the year in which an entity (typically a player or team) participated in its first One Day International (ODI) cricket match.
-
C.
odiMatchesPlayed
chosen
Indicates the number of One Day International (ODI) cricket matches that have been played by or between the referenced entities.
-
D.
matchOf
Indicates that one entity is a specific match, counterpart, or corresponding instance of another entity within a defined context or set.
-
E.
matches
Indicates that two entities correspond to or are in agreement with each other according to some defined criteria or pattern.
- 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.