Triple
T4349571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Oaks Stakes |
E97987
|
entity |
| Predicate | isMajorEventIn |
P259
|
FINISHED |
| Object | British flat racing season |
—
|
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: British flat racing season | Statement: [The Oaks Stakes, isMajorEventIn, British flat racing season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorEventIn Context triple: [The Oaks Stakes, isMajorEventIn, British flat racing season]
-
A.
celebratedEvent
Indicates that an entity has been honored, commemorated, or festively observed as a special event.
-
B.
hasInternationalEvent
Indicates that an entity hosts, organizes, or is associated with an event involving participants or significance across multiple countries.
-
C.
significantEvent
chosen
Indicates that an event involving the entities is of notable importance or impact within a given context.
-
D.
hasMajorVenue
Indicates that an entity is associated with a primary or principal venue where its main activities or events take place.
-
E.
famousForEvent
Indicates that an entity is widely known or recognized specifically because of a particular event.
- 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_69b3454965f881908c41190bb22f0e4b |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351a840248190b88c8a7be9158d25 |
completed | March 12, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69b34f51ed7c8190b7bf5f44b56b730d |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:15 p.m.