Triple
T4386463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belmont Stakes |
E99253
|
entity |
| Predicate | stakesRecordTime |
P56300
|
FINISHED |
| Object | 2:24.00 |
—
|
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: 2:24.00 | Statement: [Belmont Stakes, stakesRecordTime, 2:24.00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stakesRecordTime Context triple: [Belmont Stakes, stakesRecordTime, 2:24.00]
-
A.
recordHeldUntil
Indicates that a record remained valid, in force, or applicable up to a specified end time or condition.
-
B.
recordHeld
Indicates that one entity possesses or maintains a particular record associated with another entity or context.
-
C.
recordHeldFrom
Indicates that a record or position was held by an entity starting from a specified point in time.
-
D.
timingOfRace
Indicates the temporal details or schedule associated with a race, such as its start time, duration, or overall timing.
-
E.
recordHeldIn
Indicates that a record is stored, maintained, or kept within a particular location, system, or repository.
- F. None of above. chosen
Provenance (4 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_69b3454f739481909ff6c28331f0c0b9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b352669f608190b3aa7030d8073e04 |
completed | March 12, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69b34f572efc8190bad1e5078cbcb75a |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b3501834448190bedf775a80da4778 |
completed | March 12, 2026, 11:45 p.m. |
Created at: March 12, 2026, 11:19 p.m.