Triple
T15260781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tingle Creek |
E364767
|
entity |
| Predicate | raceTypeSpecialism |
P49218
|
FINISHED |
| Object | two‑mile steeplechases |
—
|
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: two‑mile steeplechases | Statement: [Tingle Creek, raceTypeSpecialism, two‑mile steeplechases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raceTypeSpecialism Context triple: [Tingle Creek, raceTypeSpecialism, two‑mile steeplechases]
-
A.
raceTypeDetail
chosen
Indicates the specific category or classification of a race, providing detailed information about the type of race involved in the relationship.
-
B.
ridingSpecialty
Indicates that one entity has a particular area of expertise or focus related to riding (e.g., a specific riding style, discipline, or type).
-
C.
racecourseType
Indicates the specific kind or classification of a racecourse associated with an entity.
-
D.
raceTypeBySex
Indicates that a race or competition is categorized or defined based on the sex of its participants.
-
E.
raceCategory
Indicates the classification of an entity into a specific race or racial group within a defined categorization system.
- 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0084e85a08190b8e63598b9f6a535 |
completed | April 15, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69deca8d1bd48190a4b94f29b425e335 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:14 a.m.