Triple
T26566173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kentucky Futurity |
E666390
|
entity |
| Predicate | horseAgeRestriction |
P160646
|
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: [Kentucky Futurity, horseAgeRestriction, 3-year-olds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: horseAgeRestriction Context triple: [Kentucky Futurity, horseAgeRestriction, 3-year-olds]
-
A.
hasAgeGuidelines
Indicates that there are specified age-related rules or recommendations governing how something should be accessed, used, or engaged with.
-
B.
ageLimitYears
Indicates the maximum allowed age, expressed in years, for which something is valid, permitted, or applicable.
-
C.
isAgeRestricted
Indicates that access to or use of something is limited based on the age of the person involved.
-
D.
ageLimitType
Indicates the type or category of age restriction that applies to an entity or activity.
-
E.
ageLimitAppliesAt
Indicates the specific age or point in time at which an age-related restriction or limit becomes effective for an entity.
- 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_69ee9cf7e94481909f0d556b36e43572 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6149f29c88190b4899c61a28828c1 |
completed | May 2, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f6037bf7a081908862a8359be80cf8 |
completed | May 2, 2026, 2 p.m. |
Created at: April 27, 2026, 1:55 a.m.