Triple
T17791100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sussex Stakes |
E444162
|
entity |
| Predicate | qualificationExtendedTo |
P128934
|
FINISHED |
| Object | three-year-olds and older horses |
—
|
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: three-year-olds and older horses | Statement: [Sussex Stakes, qualificationExtendedTo, three-year-olds and older horses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: qualificationExtendedTo Context triple: [Sussex Stakes, qualificationExtendedTo, three-year-olds and older horses]
-
A.
providedQualificationFor
Indicates that one entity supplied or granted a qualification, credential, or certification that another entity possesses or uses.
-
B.
qualificationLeadsTo
Indicates that obtaining a particular qualification results in or enables a subsequent outcome, status, or opportunity.
-
C.
qualifyingFor
Indicates that one entity meets the necessary conditions or criteria to be eligible for another entity, status, or action.
-
D.
qualificationHeld
Indicates that an entity possesses or has obtained a particular qualification or credential.
-
E.
hasQualification
Indicates that an entity possesses a specific qualification, credential, or competency.
- 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_69d8b9efe370819095cd219b143ae727 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48797408081908c48d98e1525ae87 |
completed | April 19, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69e3db7704588190a34a422421152173 |
completed | April 18, 2026, 7:28 p.m. |
Created at: April 10, 2026, 10:13 a.m.