Triple
T5588237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kempton Park Racecourse |
E146808
|
entity |
| Predicate | hasCourseShape |
P20126
|
FINISHED |
| Object | triangular |
—
|
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: triangular | Statement: [Kempton Park Racecourse, hasCourseShape, triangular]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCourseShape Context triple: [Kempton Park Racecourse, hasCourseShape, triangular]
-
A.
courseShape
chosen
Indicates the geometric layout or configuration that defines the path or outline of a course.
-
B.
hasCoursePattern
Indicates that an entity follows, is associated with, or is defined by a particular course structure or pattern.
-
C.
hasPrimaryCourse
Indicates that an entity is associated with its main or principal course in a given context (such as a meal, curriculum, or sequence of offerings).
-
D.
hasCoursePar
Indicates that one course is a parent or higher-level course in relation to another course, such as a prerequisite or overarching course.
-
E.
courseType
Indicates the classification or category of a course based on its nature, level, or instructional format.
- 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_69c009036c408190981a8d690b679b67 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0209e892c8190b936a05ef2a14d36 |
completed | March 22, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69c01b16b9bc8190ab0b945507d90e05 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:38 p.m.