Triple
T20715582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twenty20 cricket |
E509159
|
entity |
| Predicate | fieldingEmphasis |
P66555
|
FINISHED |
| Object | athleticism and run-saving |
—
|
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: athleticism and run-saving | Statement: [Twenty20 cricket, fieldingEmphasis, athleticism and run-saving]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldingEmphasis Context triple: [Twenty20 cricket, fieldingEmphasis, athleticism and run-saving]
-
A.
fieldingSpecialty
Indicates a player's particular area of expertise or primary role when performing defensive (fielding) duties in a sport.
-
B.
fieldingAbility
chosen
Indicates the level or quality of an entity’s skill and effectiveness in performing fielding actions in a game or sport.
-
C.
fielderThrows
Indicates that a fielder throws the ball, typically to another player or toward a base.
-
D.
fielderMittFeature
Indicates that a baseball fielder’s mitt possesses or includes a particular feature or characteristic.
-
E.
fieldedIn
Indicates that an entity was deployed, presented, or put into active use within a particular context, event, or domain.
- 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.