Triple
T22844442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prix du Jockey Club |
E566174
|
entity |
| Predicate | racecourseSetting |
P149934
|
FINISHED |
| Object | Chantilly forest surroundings |
—
|
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: Chantilly forest surroundings | Statement: [Prix du Jockey Club, racecourseSetting, Chantilly forest surroundings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: racecourseSetting Context triple: [Prix du Jockey Club, racecourseSetting, Chantilly forest surroundings]
-
A.
racecourseFeature
Indicates that one entity is a physical or functional feature or component of a racecourse associated with the other entity.
-
B.
racecourseManaged
Indicates that one entity is responsible for operating, organizing, or overseeing the management of a racecourse for another entity.
-
C.
racecourseType
Indicates the specific kind or classification of a racecourse associated with an entity.
-
D.
racecourseOpened
Indicates that a racecourse began operating or was officially opened on a specified date or at a specified time.
-
E.
raceTrack
Indicates that one entity serves as a race track or racing course used by another entity for racing activities.
- 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_69e245869e188190a196584f36e682da |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17e8726d4819095b4d999b4172ff7 |
completed | April 29, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69eed2d117088190acbfe130d84f8627 |
completed | April 27, 2026, 3:06 a.m. |
| PDg | Predicate description generation | batch_69eeeb577e2081909f4a4e9c296535c0 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:36 p.m.