Triple
T21486632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Boon |
E530131
|
entity |
| Predicate | TestBattingAverage |
P64579
|
FINISHED |
| Object | 43.65 |
—
|
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: 43.65 | Statement: [David Boon, TestBattingAverage, 43.65]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: TestBattingAverage Context triple: [David Boon, TestBattingAverage, 43.65]
-
A.
testBattingAverage
chosen
Indicates that an entity evaluates or measures the batting average performance of another entity or subject.
-
B.
battingAverageTest
Indicates the statistical relationship between a batter’s number of hits and official at-bats used to evaluate hitting performance.
-
C.
testBowlingAverage
Indicates the action of evaluating or verifying an entity’s bowling average, typically by checking its value or performance against expected criteria.
-
D.
battingAverage
Indicates the statistical relationship between a batter’s number of hits and official at-bats, expressing how often they successfully get a hit.
-
E.
odiBattingAverage
Indicates the batting average a player has achieved in One Day International (ODI) cricket matches.
- 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_69e0c45acc3881908e38d3f28964152b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea370adc8190b79fe26e2eba1dca |
completed | April 23, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69e631f6e68081908f5ee4ce7413803e |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:22 p.m.