Triple
T18319347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exceed And Excel |
E438827
|
entity |
| Predicate | breedingImpact |
P121603
|
FINISHED |
| Object | highly influential sire of sprinters |
—
|
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: highly influential sire of sprinters | Statement: [Exceed And Excel, breedingImpact, highly influential sire of sprinters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: breedingImpact Context triple: [Exceed And Excel, breedingImpact, highly influential sire of sprinters]
-
A.
impactOnReproduction
chosen
Indicates a relationship where one entity affects, alters, or influences the reproductive capacity, success, or processes of another entity.
-
B.
breedingUse
Indicates that one entity is used for breeding or reproductive purposes with respect to another entity.
-
C.
breedingGoal
Indicates that one entity is the intended objective or target outcome of a breeding process involving another entity.
-
D.
breedingTrait
Indicates that an entity possesses a heritable characteristic that is relevant or targeted in a breeding process or program.
-
E.
breedingType
Indicates the method or strategy by which organisms reproduce or are bred.
- 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_69e50aa4d3308190883714e1ef6a1d84 |
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.