Triple
T26209489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cricket |
E655443
|
entity |
| Predicate | hasT20Limit |
P57803
|
FINISHED |
| Object | 20 overs per side |
—
|
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 per side | Statement: [Cricket, hasT20Limit, 20 overs per side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasT20Limit Context triple: [Cricket, hasT20Limit, 20 overs per side]
-
A.
isLimitOf
Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
-
B.
usesLimitedOversRules
chosen
Indicates that the action or event is conducted under limited-overs rules, typically involving a fixed maximum number of overs per side.
-
C.
hasLimitation
Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
-
D.
T20IDebutFor
Indicates that an entity made its Twenty20 International (T20I) debut while representing a specified team or side.
-
E.
hasLimitSet
Indicates that there is a defined boundary, range, or constraint applied to something.
- 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_69ee5b49adb4819086545280d4ef6337 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60d160f60819087ee6aac626327ea |
completed | May 2, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69f5b007ec1c819092e2c3605933f60b |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:52 p.m.