Triple
T16626901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glasgow Stakes |
E403969
|
entity |
| Predicate | raceStatusHistory |
P123621
|
FINISHED |
| Object | Has held Listed status |
—
|
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: Has held Listed status | Statement: [Glasgow Stakes, raceStatusHistory, Has held Listed status]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raceStatusHistory Context triple: [Glasgow Stakes, raceStatusHistory, Has held Listed status]
-
A.
raceStatus
Indicates the current state or progress of an entity’s participation in a race or competitive event.
-
B.
raceRecord
Indicates that there exists a recorded result or performance entry for an entity participating in a race or competitive event.
-
C.
notableRaceStatus
Indicates that an entity holds a distinguished or significant status in the context of a particular race or racing event.
-
D.
raceWins
Indicates that one participant wins or finishes ahead of another in a race or competitive event.
-
E.
raceRecordSummary
Indicates a summarized record of outcomes or performance across one or more races involving the related entities.
- 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_69d883897eb481909eaaa088ba9918d9 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e375530ed081908337dc5c6360d733 |
completed | April 18, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69e296ad3f148190af09223dc35b155c |
completed | April 17, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69e2d7fb02f481908885a226c2191231 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:17 a.m.