Triple
T18320492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stonestreet Stables |
E438861
|
entity |
| Predicate | breedsHorse |
P128446
|
FINISHED |
| Object | Curlin progeny |
—
|
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: Curlin progeny | Statement: [Stonestreet Stables, breedsHorse, Curlin progeny]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: breedsHorse Context triple: [Stonestreet Stables, breedsHorse, Curlin progeny]
-
A.
horseBreed
Indicates that one entity is a specific breed of the horse represented by the other entity.
-
B.
featuresHorse
Indicates that something includes, presents, or prominently involves a horse as a central element or subject.
-
C.
horseName
Indicates that an entity has the specified name of a horse.
-
D.
notableHorseBred
chosen
Indicates that one entity is a notable horse that was bred by the other entity.
-
E.
thoroughbredFamily
Indicates that one entity belongs to, or is classified within, a specific Thoroughbred horse family lineage 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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50aa5a3508190a3025e71c11d79e2 |
completed | April 19, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69e44fe4ee10819086b4142444fca1f5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:36 a.m.