Triple
T20401164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Randy Johnson |
E500332
|
entity |
| Predicate | broke300WinMilestoneDate |
P38938
|
FINISHED |
| Object | 2009-06-04 |
—
|
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: 2009-06-04 | Statement: [Randy Johnson, broke300WinMilestoneDate, 2009-06-04]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broke300WinMilestoneDate Context triple: [Randy Johnson, broke300WinMilestoneDate, 2009-06-04]
-
A.
broke300WinMilestoneYear
chosen
Indicates the year in which an entity (typically a pitcher) achieved or surpassed the milestone of 300 career wins.
-
B.
brokeSoundBarrierDate
Indicates the date on which an entity first exceeded the speed of sound.
-
C.
brokeRecordOf
Indicates that one entity has surpassed or exceeded a previous performance or achievement previously held by another entity.
-
D.
battingMilestone
Indicates reaching a significant achievement or benchmark related to batting performance, such as a notable run total or record.
-
E.
brokeRecord
Indicates that one entity surpassed a previous best performance or achievement standard set by another (or itself) in a given domain.
- 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_69e0b4a81bec8190b69adfdc1336a015 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6798e7a588190b60bd54260e540f4 |
completed | April 20, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_69e5765d7cb48190adec18d6d1e3d263 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:29 a.m.