Triple
T22031046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gazelle Stakes |
E544085
|
entity |
| Predicate | grading |
P146346
|
FINISHED |
| Object | Grade II |
—
|
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: Grade II | Statement: [Gazelle Stakes, grading, Grade II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grading Context triple: [Gazelle Stakes, grading, Grade II]
-
A.
gradeIn
Indicates that an entity has a particular grade or score within a specified course, assignment, or evaluation context.
-
B.
grades
Indicates that one entity evaluates and assigns a score or level of performance to another entity.
-
C.
gradeWithin
Indicates that one value’s grade or level falls within a specified range or interval relative to another.
-
D.
gradeCategory
Indicates the classification of a grade into a broader category or level (such as letter grade, performance band, or pass/fail group).
-
E.
gradingSystem
Indicates the method or criteria by which performance, quality, or achievement is evaluated and assigned a grade or score.
- 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_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. |
| PDg | Predicate description generation | batch_69e6fad4a540819096cdd5ea08527220 |
completed | April 21, 2026, 4:19 a.m. |
Created at: April 16, 2026, 8:24 p.m.