Triple
T18319386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape Cross |
E438828
|
entity |
| Predicate | sireOfGoldenHornAchievement |
P129557
|
FINISHED |
| Object | winner of Derby and Prix de l'Arc de Triomphe |
—
|
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: winner of Derby and Prix de l'Arc de Triomphe | Statement: [Cape Cross, sireOfGoldenHornAchievement, winner of Derby and Prix de l'Arc de Triomphe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sireOfGoldenHornAchievement Context triple: [Cape Cross, sireOfGoldenHornAchievement, winner of Derby and Prix de l'Arc de Triomphe]
-
A.
hasHorns
Indicates that an entity possesses horns as a physical feature.
-
B.
hasFounderAchievement
Indicates that an entity has received or holds a notable achievement, recognition, or award specifically in its role as a founder.
-
C.
hasMainAchievement
Indicates that an entity possesses a primary or most significant achievement associated with it.
-
D.
sireOf
chosen
Indicates that one entity is the male parent (father) of another entity.
-
E.
lionCrowned
Indicates that an entity (typically a lion) is depicted or described as wearing a crown, symbolizing rulership, authority, or elevated status.
- 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.