Triple
T18110796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Investec Oaks |
E433467
|
entity |
| Predicate | hasRaceTypeDetail |
P49218
|
FINISHED |
| Object | flat racing for Thoroughbreds |
—
|
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: flat racing for Thoroughbreds | Statement: [Investec Oaks, hasRaceTypeDetail, flat racing for Thoroughbreds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRaceTypeDetail Context triple: [Investec Oaks, hasRaceTypeDetail, flat racing for Thoroughbreds]
-
A.
hasRaceClass
Indicates that an entity participates in or is associated with a particular race classification or category.
-
B.
hasRace
Indicates that an entity possesses or is characterized by a particular race or racial classification.
-
C.
raceTypeDetail
chosen
Indicates the specific category or classification of a race, providing detailed information about the type of race involved in the relationship.
-
D.
hasRaceFormat
Indicates that an entity is associated with, or characterized by, a particular race format or type of race structure.
-
E.
hasRaceSurface
Indicates that an event or activity takes place on, or is associated with, a specific type of race surface.
- 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddd2038081909515fb6d17495cbf |
completed | April 19, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_69e43313ca788190baa224269e71de49 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:28 a.m.