Triple
T21730669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sirenia Stakes |
E536395
|
entity |
| Predicate | elevatedToGroup3 |
P131291
|
FINISHED |
| Object | 2006 |
—
|
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: 2006 | Statement: [Sirenia Stakes, elevatedToGroup3, 2006]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevatedToGroup3 Context triple: [Sirenia Stakes, elevatedToGroup3, 2006]
-
A.
upgradedToGroup3
chosen
Indicates that an entity has been changed or elevated from its previous status or category to membership in group 3.
-
B.
elevatedTo
Indicates that one entity is promoted or raised to a higher rank, status, position, or level relative to another.
-
C.
promotedToGroup2
Indicates that an entity has been advanced or elevated in status, role, or membership into a second-level group or category.
-
D.
upgradedToGroup1
Indicates that an entity has been elevated or transitioned to a higher-status category or group labeled "Group 1".
-
E.
upgradedToGroup1From
Indicates that an entity has been elevated or transitioned into group 1 status from another specified source group or category.
- 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_69e0c46d3284819099a4f9d5a704eb95 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69effd064fcc819084852b4248f65a81 |
completed | April 28, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e6969c16fc8190b5126c169317d85d |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:48 p.m.