Triple
T19055172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steve Smith |
E466374
|
entity |
| Predicate | testBattingAverageOver50 |
P64579
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Steve Smith, testBattingAverageOver50, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testBattingAverageOver50 Context triple: [Steve Smith, testBattingAverageOver50, true]
-
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.
battingAverage
Indicates the statistical relationship between a batter’s number of hits and official at-bats, expressing how often they successfully get a hit.
-
D.
odiBattingAverage
Indicates the batting average a player has achieved in One Day International (ODI) cricket matches.
-
E.
battingAverageCategory
Indicates the classification of an entity’s batting average into a defined performance category (e.g., low, medium, high).
- 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_69d8dd040fb881909af2a964f65ad208 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5dc056b708190a2b84cbddf0fc2d9 |
completed | April 20, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69e4b99633c8819097988608c278ecf8 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:03 p.m.