Triple
T30961760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Festival Trials Day |
E788844
|
entity |
| Predicate | heldOnCourse |
P170845
|
FINISHED |
| Object | Cheltenham New Course |
—
|
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: Cheltenham New Course | Statement: [Festival Trials Day, heldOnCourse, Cheltenham New Course]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldOnCourse Context triple: [Festival Trials Day, heldOnCourse, Cheltenham New Course]
-
A.
heldOn
Indicates that an event or activity takes place at a specific time, date, or occasion.
-
B.
heldTo
Indicates that one entity is obligated, bound, or accountable to another entity, standard, or agreement.
-
C.
heldAlong
Indicates that one entity is held or supported in a position that follows or runs parallel to the length or course of another entity.
-
D.
heldEvery
Indicates that an entity consistently possessed or maintained control of another entity throughout every instance or period within a specified range.
-
E.
heldAs
Indicates that one entity is kept, maintained, or regarded in a particular state, role, or condition by another entity.
- 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_69f224c3a6b48190951add9b7b7f0271 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695f9fe7c819084322bf6cdc70a13 |
completed | May 3, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f695385a2881908cc28ef97fffc867 |
completed | May 3, 2026, 12:22 a.m. |
Created at: April 29, 2026, 8:54 p.m.