Triple
T6515369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rogers Hornsby |
E148242
|
entity |
| Predicate | wonTripleCrown |
P14877
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Rogers Hornsby, wonTripleCrown, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wonTripleCrown Context triple: [Rogers Hornsby, wonTripleCrown, yes]
-
A.
yearsSincePreviousTripleCrown
Indicates the number of years that have elapsed since the most recent prior occurrence of a Triple Crown.
-
B.
previousTripleCrownWinner
Indicates that one entity is the Triple Crown winner who immediately preceded the other entity in time.
-
C.
tripleCrownYear
Indicates the year in which an entity achieved a Triple Crown title or completed a Triple Crown accomplishment.
-
D.
tripleCrownWinner
chosen
Indicates that an entity has won all three major titles or championships that together constitute a "Triple Crown" within a particular sport or competitive domain.
-
E.
tripleCrownStatus
Indicates whether an entity has achieved, is pursuing, or holds a specific standing related to a recognized "triple crown" set of three major accomplishments or titles.
- 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_69c687e68e748190baceb9298f32d3ed |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ac0d395081908fe6b1f9a912f095 |
completed | March 27, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69c68ab98c78819081743e614df04e1d |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:44 p.m.