Triple
T4386446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belmont Stakes |
E99253
|
entity |
| Predicate | tripleCrownLegNumber |
P56297
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Belmont Stakes, tripleCrownLegNumber, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tripleCrownLegNumber Context triple: [Belmont Stakes, tripleCrownLegNumber, 3]
-
A.
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.
-
B.
tripleCrownYear
Indicates the year in which an entity achieved a Triple Crown title or completed a Triple Crown accomplishment.
-
C.
yearsSincePreviousTripleCrown
Indicates the number of years that have elapsed since the most recent prior occurrence of a Triple Crown.
-
D.
tripleCrownWinner
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.
developedTripleCrownIn
Indicates that an entity created or brought into existence the Triple Crown within a specified context or location.
- 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_69b3454f739481909ff6c28331f0c0b9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b352669f608190b3aa7030d8073e04 |
completed | March 12, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69b34f572efc8190bad1e5078cbcb75a |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b3501834448190bedf775a80da4778 |
completed | March 12, 2026, 11:45 p.m. |
Created at: March 12, 2026, 11:19 p.m.