Triple
T13758067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hank Aaron |
E330526
|
entity |
| Predicate | broke |
P110842
|
FINISHED |
| Object | Babe Ruth's career home run record |
—
|
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: Babe Ruth's career home run record | Statement: [Hank Aaron, broke, Babe Ruth's career home run record]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broke Context triple: [Hank Aaron, broke, Babe Ruth's career home run record]
-
A.
broken
Indicates that an entity is damaged or no longer functioning as intended, often as the result of some prior action or event.
-
B.
brokenUpAt
Indicates that a romantic or close relationship between two entities ended at a specific time or date.
-
C.
brokenUp
Indicates that a previously existing romantic or close relationship between two entities has ended.
-
D.
break
Indicates that one entity causes another entity to separate into pieces, stop functioning, or otherwise lose its normal integrity or continuity.
-
E.
breaksWith
Indicates that one entity ends or disrupts an existing association, agreement, or alignment with another entity.
- 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_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. |
| PDg | Predicate description generation | batch_69dbc59db0148190bcaf9646403ca64f |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 10:09 p.m.