Triple
T15338105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cheltenham Gold Cup |
E366719
|
entity |
| Predicate | recordConsecutiveWinsCount |
P13514
|
FINISHED |
| Object | 5 |
—
|
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: 5 | Statement: [Cheltenham Gold Cup, recordConsecutiveWinsCount, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordConsecutiveWinsCount Context triple: [Cheltenham Gold Cup, recordConsecutiveWinsCount, 5]
-
A.
mostConsecutiveWinsCount
chosen
Indicates the highest number of wins achieved in a row within a given sequence or context.
-
B.
consecutiveWinsInSeason
Indicates that one entity achieved a specified number of back-to-back victories within a single season.
-
C.
consecutiveGamesRecordHeldFrom
Indicates that one entity held the record for most consecutive games played starting from a specified point in time.
-
D.
consecutiveGamesRecordHeldUntil
Indicates that an entity held the record for most consecutive games until a specified later point in time or event.
-
E.
consecutiveWinningSeasons
Indicates that an entity (such as a team or individual) has achieved winning seasons in back-to-back or uninterrupted consecutive years.
- 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_69d85a1355608190a6673ddb67231d54 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e11b22c81908280efe65acd5454 |
completed | April 16, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_69deca9659f48190b8661df223ce5078 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:17 a.m.