Triple
T5251152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Derby City |
E118589
|
entity |
| Predicate | hasAssociatedSport |
P15165
|
FINISHED |
| Object | horse racing |
—
|
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: horse racing | Statement: [Derby City, hasAssociatedSport, horse racing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedSport Context triple: [Derby City, hasAssociatedSport, horse racing]
-
A.
associatedWithTeamSport
Indicates a relationship where an entity is connected to, involved in, or participates in a team-based sport.
-
B.
includesSport
chosen
Indicates that one entity contains, offers, or features a particular sport as part of its activities, content, or composition.
-
C.
hasRelativeInSport
Indicates that one entity has a family member who participates or is involved in a sport-related activity or profession.
-
D.
associatedWithSportMarket
Indicates a relationship where an entity is connected or linked to a specific sport-related market or segment within the sports industry.
-
E.
hasEsport
Indicates that an entity is associated with or participates in a specific electronic sports (esports) activity or competition.
- 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_69bd446978108190bb5f9c5c23d93f88 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b7b840881908bb1ecb8a0047382 |
completed | March 20, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69bd77c30bac8190a883ca45da35d667 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:50 p.m.