Triple
T4573822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1999 Cricket World Cup |
E123095
|
entity |
| Predicate | cricketFormat |
P2673
|
FINISHED |
| Object | Limited overs |
—
|
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: Limited overs | Statement: [1999 Cricket World Cup, cricketFormat, Limited overs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cricketFormat Context triple: [1999 Cricket World Cup, cricketFormat, Limited overs]
-
A.
competitionFormat
chosen
Indicates the specific structure or ruleset under which a competition is organized and conducted.
-
B.
traditionalCricketTeam
Indicates that an entity is a cricket team organized and composed according to customary or historically established rules and structures of the sport.
-
C.
WorldSeriesFormat
Indicates the specific competitive structure or rules used to organize and play a World Series matchup.
-
D.
captainODI
Indicates that the subject serves as the captain of the object’s team in One Day International (ODI) cricket matches.
-
E.
replacedCompetitionFormat
Indicates that one competition format was substituted for and took the place of another competition format.
- 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_69bd46466c7081909d07f36be2d08804 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd58c89a5c81909a78bf0ac64777ad |
completed | March 20, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69bd5227063c8190973155a875b013a7 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:10 p.m.