Triple
T7768595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arky Vaughan |
E179011
|
entity |
| Predicate | battingAverageIn1935 |
P78229
|
FINISHED |
| Object | .385 |
—
|
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: .385 | Statement: [Arky Vaughan, battingAverageIn1935, .385]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battingAverageIn1935 Context triple: [Arky Vaughan, battingAverageIn1935, .385]
-
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.
careerBattingAverage
Indicates the long-term batting performance of a player, calculated as their total hits divided by total at-bats over their entire career.
-
C.
odiBattingAverage
Indicates the batting average a player has achieved in One Day International (ODI) cricket matches.
-
D.
testBattingAverage
Indicates that an entity evaluates or measures the batting average performance of another entity or subject.
-
E.
battingAverageTest
Indicates the statistical relationship between a batter’s number of hits and official at-bats used to evaluate hitting performance.
- 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_69c69f30602c819082ab52cd4af5c592 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c704376dc08190890f5ebb9f259cfd |
completed | March 27, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69c7016f4ce881909c2e9f610255187b |
completed | March 27, 2026, 10:15 p.m. |
| PDg | Predicate description generation | batch_69c702a78edc819090c3448d33c8c381 |
completed | March 27, 2026, 10:20 p.m. |
Created at: March 27, 2026, 4:11 p.m.