Triple
T16338870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Test cricket |
E396743
|
entity |
| Predicate | battingConditions |
P123026
|
FINISHED |
| Object | change over multiple days |
—
|
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: change over multiple days | Statement: [Test cricket, battingConditions, change over multiple days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battingConditions Context triple: [Test cricket, battingConditions, change over multiple days]
-
A.
usesLimitedOversRules
Indicates that the action or event is conducted under limited-overs rules, typically involving a fixed maximum number of overs per side.
-
B.
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.
-
C.
ballsAndStrikes
Indicates the relationship between a pitch and how it is judged in baseball as either a ball or a strike.
-
D.
battingType
Indicates the style or handedness with which a player bats (e.g., right-handed, left-handed, or both).
-
E.
subsequentInningOutcome
Indicates the result or event that occurs in the inning immediately following a given reference inning.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2da08fbc88190a31127d10ca633d6 |
completed | April 18, 2026, 1:10 a.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24555bb6c8190977cf5c5f9149056 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:07 a.m.