Triple
T17770843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Wales's Stakes |
E443631
|
entity |
| Predicate | breedsEligible |
P41121
|
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: [Prince of Wales's Stakes, breedsEligible, Thoroughbred]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: breedsEligible Context triple: [Prince of Wales's Stakes, breedsEligible, Thoroughbred]
-
A.
hasBreedRegistry
Indicates that an animal or breed is officially recorded or recognized in a specific breed registry or studbook.
-
B.
associatedAnimalBreed
chosen
Indicates that there is a relationship linking an entity to a specific breed of animal with which it is connected or identified.
-
C.
isExhibitionBreed
Indicates that an animal belongs to a breed that is recognized or suitable for formal exhibition or show competitions.
-
D.
isHeritageBreed
Indicates that an animal breed belongs to a traditional, historically established lineage recognized for its cultural, genetic, or agricultural heritage.
-
E.
breed
Indicates that an organism reproduces to generate offspring, typically with another organism of the same species.
- 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_69d8b9edf16c8190a59ebd245d378f4f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e485ff928481909fe32260ba57978f |
completed | April 19, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:11 a.m.