Triple
T18599277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2008 Asia Cup |
E454575
|
entity |
| Predicate | finalResultMargin |
P39190
|
FINISHED |
| Object | 100 runs |
—
|
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: 100 runs | Statement: [2008 Asia Cup, finalResultMargin, 100 runs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalResultMargin Context triple: [2008 Asia Cup, finalResultMargin, 100 runs]
-
A.
finalRoundMargin
chosen
Indicates the point or score difference between competitors in the final round of a contest or competition.
-
B.
defeatedByMargin
Indicates that one entity was defeated by another with a specified numerical margin or difference in score, votes, or performance.
-
C.
finalScore
Indicates the resulting or overall score achieved after all contributing actions, events, or evaluations are completed.
-
D.
marginOf
Indicates the difference or buffer between two related quantities, values, or boundaries, often expressing how much one exceeds or falls short of another.
-
E.
finalMatchDetermines
Indicates that the outcome of a final match decides or establishes a particular result, status, or consequence for the related entities.
- 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5474f1d548190b74408eabd396344 |
completed | April 19, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69e478cf5e888190a0b1074b0c6525df |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:45 a.m.