Triple
T37328060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stuart Broad |
E926663
|
entity |
| Predicate | bowlingStyleInTests |
P65539
|
FINISHED |
| Object | right-arm fast-medium |
—
|
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: right-arm fast-medium | Statement: [Stuart Broad, bowlingStyleInTests, right-arm fast-medium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bowlingStyleInTests Context triple: [Stuart Broad, bowlingStyleInTests, right-arm fast-medium]
-
A.
bestBowlingInTests
Indicates the record or performance representing the most outstanding bowling figures achieved in Test cricket.
-
B.
associatedWithBowlingStyleOfPerson
chosen
Indicates a relationship where something is linked to or characterized by the specific bowling style used by a person.
-
C.
bowlingAverageInTests
Indicates the bowling average a player has achieved in Test cricket matches.
-
D.
bowlingStrength
Indicates the degree or effectiveness of one entity’s bowling performance or capability in relation to another.
-
E.
associatedWithBattingStyleOfPerson
Indicates a relationship where something is connected to or characterized by the batting style of a specific person.
- 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_69f76eb386d88190a8d511aa11540dfc |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.