Triple
T17963481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2019 Cricket World Cup |
E449140
|
entity |
| Predicate | winnerFirstTitle |
P57793
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [2019 Cricket World Cup, winnerFirstTitle, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: winnerFirstTitle Context triple: [2019 Cricket World Cup, winnerFirstTitle, true]
-
A.
winnerTitle
Indicates the formal title or designation awarded to the entity that wins a particular competition, contest, or event.
-
B.
firstTitleForWinner
chosen
Indicates that the associated title is the first title ever won by the specified winner.
-
C.
winnerFirstShieldTitle
Indicates that the subject is the winner whose first Shield title (e.g., in a specific competition or season) is being referenced.
-
D.
winnerTitleRecord
Indicates that a record documents the title or achievement associated with an entity that has won a particular contest, award, or competition.
-
E.
wonTitleWith
Indicates that an entity secured a specific title, award, or championship while being associated with or representing another entity (such as a team, organization, or group).
- 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_69d8b9f9927c8190a006110c8b996e61 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b135cd2c8190a6190cf6611dbe08 |
completed | April 19, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69e3f8fa62688190a5d5c361ab896256 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:22 a.m.