Triple
T34024003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coffs Harbour Racing Club |
E872457
|
entity |
| Predicate | typeOfRacecourse |
P69994
|
FINISHED |
| Object | thoroughbred |
—
|
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: thoroughbred | Statement: [Coffs Harbour Racing Club, typeOfRacecourse, thoroughbred]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfRacecourse Context triple: [Coffs Harbour Racing Club, typeOfRacecourse, thoroughbred]
-
A.
racecourseType
chosen
Indicates the specific kind or classification of a racecourse associated with an entity.
-
B.
raceTypeDetail
Indicates the specific category or classification of a race, providing detailed information about the type of race involved in the relationship.
-
C.
hasRacecourse
Indicates that an entity possesses, contains, or is associated with a racecourse facility or track.
-
D.
racecourseUsed
Indicates that a particular racecourse is utilized or employed for a given event, activity, or purpose.
-
E.
racecourseFeature
Indicates that one entity is a physical or functional feature or component of a racecourse associated with the other entity.
- 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_69f349a19ad88190ab586f010c804a8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a01185c46f0819089b4a2ad3c3e2f33 |
completed | May 10, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_6a0117e19e008190870663dd45084416 |
completed | May 10, 2026, 11:42 p.m. |
Created at: May 1, 2026, 1:51 a.m.