Triple
T36987981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coolmore Stud |
E915015
|
entity |
| Predicate | notableStallion |
P55481
|
FINISHED |
| Object | Sadler's Wells |
E1146602
|
NE 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: Sadler's Wells | Statement: [Coolmore Stud, notableStallion, Sadler's Wells]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableStallion Context triple: [Coolmore Stud, notableStallion, Sadler's Wells]
-
A.
notableStallionStood
chosen
Indicates that a notable stallion was stationed, kept, or used for breeding at a particular location or stud.
-
B.
notableHorse
Indicates that the subject is a horse recognized for particular significance, fame, or distinction.
-
C.
notableHorseBred
Indicates that one entity is a notable horse that was bred by the other entity.
-
D.
sireOfSires
Indicates that an entity is the male ancestor (a sire) of other sires, i.e., it fathers individuals who themselves become sires.
-
E.
notableGiant
Indicates that an entity is recognized as a giant of particular note, standing out for its exceptional size, influence, or significance relative to others of its kind.
- F. None of above.
Provenance (4 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_69f76e8dd0408190b8b46da118ea5128 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3e2c52dae4819081c1f0291a849d7d |
completed | June 26, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.