Triple
T4902490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belmont Stakes |
E109832
|
entity |
| Predicate | legNumberInTripleCrown |
P56298
|
FINISHED |
| Object | third |
—
|
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: third | Statement: [Belmont Stakes, legNumberInTripleCrown, third]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legNumberInTripleCrown Context triple: [Belmont Stakes, legNumberInTripleCrown, third]
-
A.
tripleCrownLegNumber
Indicates the specific leg or stage number within a Triple Crown series that an event or result pertains to.
-
B.
yearsSincePreviousTripleCrown
Indicates the number of years that have elapsed since the most recent prior occurrence of a Triple Crown.
-
C.
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.
-
D.
tripleCrownLegOrder
chosen
Indicates the sequential position of a specific leg within a Triple Crown series or event.
-
E.
tripleCrownSequence
Indicates that the entities participate in or represent the ordered sequence of events, titles, or achievements that together constitute a "triple crown."
- 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_69bd441180708190ba42ffb44fea533a |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd706245e48190a61d573438461c30 |
completed | March 20, 2026, 4:05 p.m. |
| PD | Predicate disambiguation | batch_69bd6c306b188190a08a7856beb76db4 |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:28 p.m.