Triple
T22031057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gazelle Stakes |
E544085
|
entity |
| Predicate | hasAgeQualification |
P145021
|
FINISHED |
| Object | 3-year-olds |
—
|
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-year-olds | Statement: [Gazelle Stakes, hasAgeQualification, 3-year-olds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAgeQualification Context triple: [Gazelle Stakes, hasAgeQualification, 3-year-olds]
-
A.
canAgeFor
Indicates that one entity is capable of undergoing an aging or maturation process for the benefit, use, or context of another entity.
-
B.
hasAge
Indicates that an entity possesses a specific age value, typically expressed as a number of time units since its birth or creation.
-
C.
hasAgeParticipation
chosen
Indicates a relationship where an entity’s participation or involvement is characterized or constrained by a specific age or age range.
-
D.
hasQualification
Indicates that an entity possesses a specific qualification, credential, or competency.
-
E.
hasQualificationCriteria
Indicates that there are specific conditions or standards that must be met for something to be considered eligible or acceptable.
- 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_69e11e2f98c8819083e11eab90942a78 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127edd5b48190a9aeb2840105c181 |
completed | April 28, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69e6f63b0d048190b241622759aab9de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:24 p.m.