Triple
T13758050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hammerin' Hank |
E330525
|
entity |
| Predicate | homeRunRecordHeldFrom |
P45562
|
FINISHED |
| Object | 1974 |
—
|
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: 1974 | Statement: [Hammerin' Hank, homeRunRecordHeldFrom, 1974]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeRunRecordHeldFrom Context triple: [Hammerin' Hank, homeRunRecordHeldFrom, 1974]
-
A.
homeRunRecordHolder
Indicates that the subject holds the record for the most home runs, typically within a specified league, season, or career context.
-
B.
homeRunRecordSurpassedBy
Indicates that one entity’s home run record has been exceeded or broken by another entity.
-
C.
homeRunRecordSurpassedYear
chosen
Indicates the year in which a given home run record was surpassed by another performance.
-
D.
homeRunSeason
Indicates that an entity (typically a player) hit a specified number of home runs during a particular season.
-
E.
careerHomeRuns
Indicates the total number of home runs an entity has hit over the entire span of their professional career.
- 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_69d81c573f288190aa2403d484fa3d49 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de022286b481908f8a801042743512 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe97846c819093b00ea117b64e0d |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 10:09 p.m.