Triple
T9024551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stuffy McInnis |
E216011
|
entity |
| Predicate | battingAverageType |
P85907
|
FINISHED |
| Object | high batting average hitter |
—
|
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: high batting average hitter | Statement: [Stuffy McInnis, battingAverageType, high batting average hitter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battingAverageType Context triple: [Stuffy McInnis, battingAverageType, high batting average hitter]
-
A.
battingAverage
Indicates the statistical relationship between a batter’s number of hits and official at-bats, expressing how often they successfully get a hit.
-
B.
odiBattingAverage
Indicates the batting average a player has achieved in One Day International (ODI) cricket matches.
-
C.
testBattingAverage
Indicates that an entity evaluates or measures the batting average performance of another entity or subject.
-
D.
careerBattingAverage
Indicates the long-term batting performance of a player, calculated as their total hits divided by total at-bats over their entire career.
-
E.
measurementUnitForBattingAverage
Indicates the unit of measurement used to express a batting average in a given context.
- F. None of above. chosen
Provenance (4 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a7b902c81909fcbdc433a1acf7a |
completed | April 1, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee132f08190940749c7c522e4c1 |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f887108819096d45a186fc137b3 |
completed | March 31, 2026, 11:58 p.m. |
Created at: March 30, 2026, 7:07 p.m.