Triple
T24903561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Derby Day |
E623643
|
entity |
| Predicate | notableRaceDistance |
P20127
|
FINISHED |
| Object | 2400 metres (Victoria Derby) |
—
|
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: 2400 metres (Victoria Derby) | Statement: [Derby Day, notableRaceDistance, 2400 metres (Victoria Derby)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRaceDistance Context triple: [Derby Day, notableRaceDistance, 2400 metres (Victoria Derby)]
-
A.
majorRaceDistance
chosen
Indicates the standard or primary distance over which a major race or competition is contested.
-
B.
notableRaceStyle
Indicates that an entity is particularly recognized for competing in, specializing in, or being associated with a specific style or category of racing.
-
C.
raceDistanceType
Indicates the specific type or category of distance over which a race is conducted.
-
D.
notableLongRun
Indicates that an entity is recognized for having a particularly long or extended duration of continuous operation, performance, or existence.
-
E.
distancePerRace
Indicates the total distance covered in a single race event or instance.
- 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_69e2fac797cc8190b30d77f4121099ac |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 18, 2026, 5:27 a.m.