Triple
T18569969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brett Lee |
E453847
|
entity |
| Predicate | bowlingAverageTest |
P120734
|
FINISHED |
| Object | 30.81 |
—
|
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: 30.81 | Statement: [Brett Lee, bowlingAverageTest, 30.81]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bowlingAverageTest Context triple: [Brett Lee, bowlingAverageTest, 30.81]
-
A.
testBowlingAverage
chosen
Indicates the action of evaluating or verifying an entity’s bowling average, typically by checking its value or performance against expected criteria.
-
B.
odiBowlingAverage
Indicates the average number of runs a bowler concedes per wicket taken in One Day International (ODI) cricket.
-
C.
battingAverageTest
Indicates the statistical relationship between a batter’s number of hits and official at-bats used to evaluate hitting performance.
-
D.
testBattingAverage
Indicates that an entity evaluates or measures the batting average performance of another entity or subject.
-
E.
battingAverage
Indicates the statistical relationship between a batter’s number of hits and official at-bats, expressing how often they successfully get a hit.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53b01331c8190bec3aba40358a843 |
completed | April 19, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69e478c16e0c8190b03966aa23c395a6 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:43 a.m.