Triple
T35547794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ryan Preece |
E1027265
|
entity |
| Predicate | hasRacingNumberHistory |
P59494
|
FINISHED |
| Object | 37 |
—
|
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: 37 | Statement: [Ryan Preece, hasRacingNumberHistory, 37]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRacingNumberHistory Context triple: [Ryan Preece, hasRacingNumberHistory, 37]
-
A.
hasRacingUseSince
Indicates that an entity has been used for racing starting from a specified point in time.
-
B.
hasRacingCode
Indicates that an entity is associated with a specific racing classification or identifier code.
-
C.
raceNumberInHistory
Indicates that an entity has a specific sequential race number within the historical record of races or events.
-
D.
raceStatusHistory
Indicates the recorded sequence of status changes or states that a race has undergone over time.
-
E.
racingNumber
chosen
Indicates that an entity has been assigned a specific competition or race identification number used to distinguish it from other participants.
- 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_69f76e008ba08190927acd8e5e0344c8 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
Created at: May 3, 2026, 4:04 p.m.