Triple
T36987977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coolmore Stud |
E915015
|
entity |
| Predicate | primaryTrainer |
P41095
|
FINISHED |
| Object | Aidan O'Brien |
E1292252
|
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: Aidan O'Brien | Statement: [Coolmore Stud, primaryTrainer, Aidan O'Brien]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryTrainer Context triple: [Coolmore Stud, primaryTrainer, Aidan O'Brien]
-
A.
trainer
chosen
Indicates a relationship where one entity teaches, coaches, or prepares another entity to develop skills, knowledge, or performance in a particular domain.
-
B.
providesTrainingFor
Indicates that one entity delivers or conducts training activities intended to develop the skills or knowledge of another entity.
-
C.
alsoTrains
Indicates that an entity, in addition to its primary role or activity, is involved in training another entity.
-
D.
trainingPartner
Indicates that two entities participate together in training activities, typically collaborating or assisting each other in practice or skill development.
-
E.
primaryTrainingFocus
Indicates the main area or aspect that training is chiefly directed toward or concentrated on.
- 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_6a3e575c55e081909dd64a3b32ab4e92 |
completed | June 26, 2026, 10:41 a.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.