Triple
T4412779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cigar |
E94888
|
entity |
| Predicate | legacyHonor |
P15675
|
FINISHED |
| Object | Cigar Mile Handicap named in his honor |
—
|
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: Cigar Mile Handicap named in his honor | Statement: [Cigar, legacyHonor, Cigar Mile Handicap named in his honor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legacyHonor Context triple: [Cigar, legacyHonor, Cigar Mile Handicap named in his honor]
-
A.
honoursLegacyOf
Indicates that one entity actively preserves, respects, or celebrates the memory, values, or achievements of another entity from the past.
-
B.
honoredThrough
chosen
Indicates that one entity is recognized or commemorated by means of another entity, event, or action.
-
C.
honorLevel
Indicates the degree or status of respect, distinction, or recognition accorded to an entity relative to others.
-
D.
clubHonour
Indicates that a club has received or been awarded a particular honour, title, or distinction.
-
E.
honors
Indicates that one entity shows respect, recognition, or esteem toward another entity, often in a formal or ceremonial way.
- 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_69b34539638c8190abfea3eb29425210 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b354e7b30c819082ee781dd202dcc4 |
completed | March 13, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69b34f5d0c54819085c08533bb58030a |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:29 p.m.