Triple
T678446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yogi Berra |
E13128
|
entity |
| Predicate | battedOver300Seasons |
P17429
|
FINISHED |
| Object | multiple |
—
|
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: multiple | Statement: [Yogi Berra, battedOver300Seasons, multiple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battedOver300Seasons Context triple: [Yogi Berra, battedOver300Seasons, multiple]
-
A.
careerRunsScored
Indicates the total number of runs an entity has scored over the entire duration of their playing career.
-
B.
isBattingTripleCrown
Indicates that a player is simultaneously leading a league in batting average, home runs, and runs batted in.
-
C.
careerBattingAverage
Indicates the long-term batting performance of a player, calculated as their total hits divided by total at-bats over their entire career.
-
D.
careerHomeRuns
Indicates the total number of home runs an entity has hit over the entire span of their professional career.
-
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. 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_69a4933d3bf88190972041cd8cf143b9 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a04e17088190943d54977eb3f83a |
completed | March 1, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69a49d1d79608190a849ba9ffad2879d |
completed | March 1, 2026, 8:10 p.m. |
| PDg | Predicate description generation | batch_69a49df19c9481909cc9bc33ed7f011b |
completed | March 1, 2026, 8:13 p.m. |
Created at: March 1, 2026, 7:36 p.m.