Triple
T14893486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hank Aaron’s 700th home run |
E359809
|
entity |
| Predicate | homeRunNumber |
P14862
|
FINISHED |
| Object | 700 |
—
|
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: 700 | Statement: [Hank Aaron’s 700th home run, homeRunNumber, 700]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeRunNumber Context triple: [Hank Aaron’s 700th home run, homeRunNumber, 700]
-
A.
homeRuns
chosen
Indicates the number of home runs a player hits, or that a specific home run event occurs, in a baseball context.
-
B.
homeRunSeason
Indicates that an entity (typically a player) hit a specified number of home runs during a particular season.
-
C.
homeRunRate
Indicates the frequency at which a player or team hits home runs relative to a specified number of opportunities (such as at-bats, plate appearances, or games).
-
D.
homeRunType
Indicates the specific kind of home run that was hit in a baseball play (e.g., solo, two-run, three-run, grand slam).
-
E.
homeRunRecordSurpassedBy
Indicates that one entity’s home run record has been exceeded or broken by another entity.
- 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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69ded5f9d10c819091732d7a5a42a682 |
completed | April 15, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69de9a4a14a88190951bb8f4c60bd37b |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:10 a.m.