Triple
T23035617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2012 Asia Cup |
E573585
|
entity |
| Predicate | finalScoreBangladesh |
P2625
|
FINISHED |
| Object | 234/8 |
—
|
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: 234/8 | Statement: [2012 Asia Cup, finalScoreBangladesh, 234/8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalScoreBangladesh Context triple: [2012 Asia Cup, finalScoreBangladesh, 234/8]
-
A.
finalScore
chosen
Indicates the resulting or overall score achieved after all contributing actions, events, or evaluations are completed.
-
B.
opponentFinalScore
Indicates the final score achieved by an opposing participant or team in a contest or game.
-
C.
finalSecondLegScore
Indicates the score achieved in the second leg of a two-leg competition or matchup once that leg is completed.
-
D.
fijiScore
Indicates a scoring relationship where an entity is assigned or associated with a specific score according to the Fiji scoring system or criteria.
-
E.
finalOfficialMatchScore
Indicates the conclusive, authoritative score assigned to a match after all reviews, adjustments, or validations are completed.
- 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_69e245b911188190bc3d96326c847969 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1850df7fc81909ee522d99d96af0d |
completed | April 29, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_69ef3ba004a48190885aece88efd1f52 |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:53 p.m.