Triple
T24903615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stakes Day |
E623645
|
entity |
| Predicate | racecourseUsed |
P157863
|
FINISHED |
| Object | Flemington Racecourse |
—
|
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: Flemington Racecourse | Statement: [Stakes Day, racecourseUsed, Flemington Racecourse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: racecourseUsed Context triple: [Stakes Day, racecourseUsed, Flemington Racecourse]
-
A.
racecourseFeature
Indicates that one entity is a physical or functional feature or component of a racecourse associated with the other entity.
-
B.
racecourseType
Indicates the specific kind or classification of a racecourse associated with an entity.
-
C.
racecourseManaged
Indicates that one entity is responsible for operating, organizing, or overseeing the management of a racecourse for another entity.
-
D.
racecourseCounty
Indicates the county in which a given racecourse is geographically located or administered.
-
E.
formerRacecourse
Indicates that a location previously functioned as a racecourse but no longer serves that purpose.
- 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_69e2fac797cc8190b30d77f4121099ac |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
| PDg | Predicate description generation | batch_69f45300bd488190bb1d4160f5534ef6 |
completed | May 1, 2026, 7:15 a.m. |
Created at: April 18, 2026, 5:27 a.m.