Triple
T26834783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pakistan Cup |
E675598
|
entity |
| Predicate | usesNetRunRate |
P162362
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Pakistan Cup, usesNetRunRate, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesNetRunRate Context triple: [Pakistan Cup, usesNetRunRate, yes]
-
A.
typicalRunRate
Indicates the usual or average rate at which an activity, process, or operation is carried out over a given period.
-
B.
usesLimitedOversRules
Indicates that the action or event is conducted under limited-overs rules, typically involving a fixed maximum number of overs per side.
-
C.
usesDuckworthLewisSternMethod
Indicates that an entity determines outcomes or targets in a limited-overs cricket match using the Duckworth–Lewis–Stern (DLS) rain-affected scoring method.
-
D.
testStrikeRate
Indicates the rate at which successful outcomes occur relative to total attempts in a testing or trial context.
-
E.
IndiansRunsScored
Indicates the number of runs that the Indians team has scored in a game or specific context.
- F. None of above. chosen
Provenance (4 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_69eee9b776448190993a60b67fcc9545 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6250321088190ae3ed1dc9f2fcd03 |
completed | May 2, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f62473a38481909b919f88ffb5b492 |
completed | May 2, 2026, 4:21 p.m. |
Created at: April 27, 2026, 5:04 a.m.