Triple
T30351788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St James's Palace Stakes |
E772013
|
entity |
| Predicate | racePattern |
P169085
|
FINISHED |
| Object | Group 1 Pattern race |
—
|
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: Group 1 Pattern race | Statement: [St James's Palace Stakes, racePattern, Group 1 Pattern race]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: racePattern Context triple: [St James's Palace Stakes, racePattern, Group 1 Pattern race]
-
A.
trackPattern
Indicates that one entity follows, monitors, or records the behavior or state of another according to a defined pattern or sequence.
-
B.
raceCode
Indicates the classification of an entity according to a standardized race or ethnicity code.
-
C.
raceBranch
Indicates that one entity is a specific branch, division, or variant within a broader race or lineage represented by another entity.
-
D.
raceTrack
Indicates that one entity serves as a race track or racing course used by another entity for racing activities.
-
E.
maskPattern
Indicates a relationship where one entity serves as a masking template or pattern that determines which parts or aspects of another entity are revealed, hidden, or transformed.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6823af4a4819095c725800c2be63e |
completed | May 2, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f679496c188190ba585792f987a1f4 |
completed | May 2, 2026, 10:23 p.m. |
Created at: April 29, 2026, 7:56 p.m.