Triple
T27143818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Close Brothers Mares’ Hurdle |
E681885
|
entity |
| Predicate | sponsorshipNameIncludes |
P15097
|
FINISHED |
| Object | Close Brothers |
—
|
NE NERFINISHED |
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: Close Brothers | Statement: [Close Brothers Mares’ Hurdle, sponsorshipNameIncludes, Close Brothers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sponsorshipNameIncludes Context triple: [Close Brothers Mares’ Hurdle, sponsorshipNameIncludes, Close Brothers]
-
A.
sponsorshipName
chosen
Indicates the name or title associated with a sponsorship relationship between entities.
-
B.
sponsorshipBrand
Indicates that one entity serves as a sponsoring brand for another entity, typically providing support, funding, or endorsement.
-
C.
sponsorshipNameAdopted
Indicates that an entity has adopted or taken on a specific sponsorship name as its official or recognized designation.
-
D.
sponsorshipRenamedFrom
Indicates that a sponsorship currently known by one name previously existed under a different, earlier name.
-
E.
includesSponsorship
Indicates that one entity’s involvement, agreement, or arrangement explicitly involves sponsorship provided by another 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_69eefacca3888190b67238d380e8f28b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6383625cc8190aa223d8ef655743c |
completed | May 2, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69f63709e4848190b5cf322e06b23fb6 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 9:10 a.m.