Triple
T30351786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St James's Palace Stakes |
E772013
|
entity |
| Predicate | racecourseUse |
P157863
|
FINISHED |
| Object | Ascot round mile |
—
|
NE NERFINISHED |
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: Ascot round mile | Statement: [St James's Palace Stakes, racecourseUse, Ascot round mile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: racecourseUse Context triple: [St James's Palace Stakes, racecourseUse, Ascot round mile]
-
A.
racecourseUsed
chosen
Indicates that a particular racecourse is utilized or employed for a given event, activity, or purpose.
-
B.
racecourseFeature
Indicates that one entity is a physical or functional feature or component of a racecourse associated with the other entity.
-
C.
racecourseType
Indicates the specific kind or classification of a racecourse associated with an entity.
-
D.
racecourseManaged
Indicates that one entity is responsible for operating, organizing, or overseeing the management of a racecourse for another entity.
-
E.
racecourseSetting
Indicates that an event, scene, or activity takes place in the context or environment of a racecourse.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 7:56 p.m.