Triple
T20715594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twenty20 cricket |
E509159
|
entity |
| Predicate | inningsEndCondition |
P29156
|
FINISHED |
| Object | 20 overs bowled |
—
|
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: 20 overs bowled | Statement: [Twenty20 cricket, inningsEndCondition, 20 overs bowled]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inningsEndCondition Context triple: [Twenty20 cricket, inningsEndCondition, 20 overs bowled]
-
A.
terminationCondition
chosen
Indicates the condition or set of conditions under which an ongoing process, activity, or relationship is brought to an end.
-
B.
terminalCondition
Indicates the condition or set of conditions under which a process, interaction, or state is considered complete and should terminate.
-
C.
terminatesOn
Indicates that one process, event, or state causes or marks the ending of another at a specific time or condition.
-
D.
returnCondition
Indicates the terms, state, or circumstances under which something that was previously given, lent, or transferred is expected or required to be returned.
-
E.
hasConditionalEnding
Indicates that one entity concludes or terminates only if a specified condition involving another entity is met.
- 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_69e0b4c40ad88190b81f77695366d328 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1d12a9481909cce3711c1c2d9f8 |
completed | April 21, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_69e5c04b31248190b9b9d91b5cb854e3 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:15 p.m.