Triple
T4902491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belmont Stakes |
E109832
|
entity |
| Predicate | usualSchedule |
P3309
|
FINISHED |
| Object | early June |
—
|
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: early June | Statement: [Belmont Stakes, usualSchedule, early June]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usualSchedule Context triple: [Belmont Stakes, usualSchedule, early June]
-
A.
typicalSchedule
chosen
Indicates the usual or standard timing and sequence of activities or events associated with an entity.
-
B.
scheduleUS
Indicates that an entity arranges or assigns a time for something specifically within the context of the United States.
-
C.
ordinary
Indicates that something or someone is typical, usual, or not special or exceptional in the relevant context.
-
D.
notableRoutine
Indicates a routine, practice, or sequence of actions that is especially prominent, well-known, or significant in some context.
-
E.
schedule
Indicates that an entity arranges for an event, task, or activity to occur at a specific time or within a defined time frame.
- 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_69bd441180708190ba42ffb44fea533a |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd706245e48190a61d573438461c30 |
completed | March 20, 2026, 4:05 p.m. |
| PD | Predicate disambiguation | batch_69bd6c306b188190a08a7856beb76db4 |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:28 p.m.