Triple
T18570911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2000 ICC KnockOut Trophy |
E453869
|
entity |
| Predicate | finalScoreIndia |
P2625
|
FINISHED |
| Object | 264/6 in 50 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: 264/6 in 50 overs | Statement: [2000 ICC KnockOut Trophy, finalScoreIndia, 264/6 in 50 overs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalScoreIndia Context triple: [2000 ICC KnockOut Trophy, finalScoreIndia, 264/6 in 50 overs]
-
A.
finalScore
chosen
Indicates the resulting or overall score achieved after all contributing actions, events, or evaluations are completed.
-
B.
finalOfficialMatchScore
Indicates the conclusive, authoritative score assigned to a match after all reviews, adjustments, or validations are completed.
-
C.
opponentFinalScore
Indicates the final score achieved by an opposing participant or team in a contest or game.
-
D.
finalSecondLegScore
Indicates the score achieved in the second leg of a two-leg competition or matchup once that leg is completed.
-
E.
winningTeamScore
Indicates the number of points or goals achieved by the team that wins a particular game or competition.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53b021ea4819095fe06be88e74133 |
completed | April 19, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69e478c16e0c8190b03966aa23c395a6 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:43 a.m.