Triple
T27143875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | County Hurdle |
E681887
|
entity |
| Predicate | raceStatusChange |
P123621
|
FINISHED |
| Object | Upgraded to Grade 3 status in 1990s |
—
|
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: Upgraded to Grade 3 status in 1990s | Statement: [County Hurdle, raceStatusChange, Upgraded to Grade 3 status in 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raceStatusChange Context triple: [County Hurdle, raceStatusChange, Upgraded to Grade 3 status in 1990s]
-
A.
raceStatus
Indicates the current state or progress of an entity’s participation in a race or competitive event.
-
B.
raceStatusHistory
chosen
Indicates the recorded sequence of status changes or states that a race has undergone over time.
-
C.
statusChange
Indicates a transition in an entity’s state or condition from one status to another over time.
-
D.
notableRaceStatus
Indicates that an entity holds a distinguished or significant status in the context of a particular race or racing event.
-
E.
raceAdded
Indicates that a race event or race-related record has been newly created or incorporated into a system or dataset.
- 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_69eefacca3888190b67238d380e8f28b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f624c3e4bc8190af9a5d9b3c30d117 |
completed | May 2, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 9:10 a.m.