Triple
T21856003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hambletonian Stakes |
E539627
|
entity |
| Predicate | eligibleGait |
P145939
|
FINISHED |
| Object | trotters |
—
|
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: trotters | Statement: [Hambletonian Stakes, eligibleGait, trotters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eligibleGait Context triple: [Hambletonian Stakes, eligibleGait, trotters]
-
A.
eligibility
Indicates that an entity meets the required conditions or qualifications to participate in, receive, or perform something.
-
B.
eligibleIn
Indicates that an entity meets the necessary conditions or criteria to qualify for participation, use, or consideration within a specified context, domain, or scope.
-
C.
eligibleOn
Indicates the date or condition from which something qualifies to begin or be considered valid or applicable.
-
D.
eligibleFrom
Indicates that a subject becomes or is considered eligible starting from a specified point in time or condition.
-
E.
eligibleBody
Indicates that an entity qualifies as an appropriate or permitted body (e.g., organization or institution) to participate in or be subject to a specified relationship or action.
- 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_69e0c47829648190bbe2d1d7033768ec |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f0d635b59c81908810480f3802b847 |
completed | April 28, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69e6be9394f88190945ddd1dc004d29d |
completed | April 21, 2026, 12:02 a.m. |
| PDg | Predicate description generation | batch_69e6d054737081908aa7112975b77475 |
completed | April 21, 2026, 1:18 a.m. |
Created at: April 16, 2026, 6:56 p.m.