Triple
T18320499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midnight Cry Stable |
E438862
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Thoroughbred racehorse ownership group |
C7374
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Thoroughbred racehorse ownership group Context triple: [Midnight Cry Stable, instanceOf, Thoroughbred racehorse ownership group]
-
A.
thoroughbred racing operation
A thoroughbred racing operation is an organized business entity that breeds, trains, manages, and races thoroughbred horses for competitive and commercial purposes.
-
B.
thoroughbred horse breeding operation
A thoroughbred horse breeding operation is a specialized agricultural enterprise focused on selectively mating registered thoroughbred horses to produce high-quality offspring for racing, sales, and bloodline improvement.
-
C.
horse racing entrepreneur
A horse racing entrepreneur is an individual who identifies, invests in, and manages business opportunities within the horse racing industry, such as owning racehorses, operating stables, organizing events, or developing related services and technologies.
-
D.
racehorse owner
chosen
A racehorse owner is an individual or entity that purchases, manages, and financially supports racehorses for competition, often collaborating with trainers and jockeys to maximize performance and returns.
-
E.
Thoroughbred retirement farm
A Thoroughbred retirement farm is a specialized facility that provides long-term care, rehabilitation, and safe pasture living for retired Thoroughbred racehorses after their racing or breeding careers end.
- F. None of above.
Provenance (1 batch)
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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:36 a.m.