Triple
T24976887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TI–Raleigh |
E625045
|
entity |
| Predicate | hadNotableRider |
P51007
|
FINISHED |
| Object | Jan Raas |
—
|
NE NERFINISHED |
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: Jan Raas | Statement: [TI–Raleigh, hadNotableRider, Jan Raas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadNotableRider Context triple: [TI–Raleigh, hadNotableRider, Jan Raas]
-
A.
hasNotableRide
Indicates that an entity is associated with a particularly remarkable or well-known ride or attraction.
-
B.
hasNotableJockey
Indicates that an entity (typically a racehorse) is or was ridden by a jockey who is considered notable or distinguished.
-
C.
hasNotableHorse
Indicates that an entity is associated with a horse that is considered notable or distinguished in some recognized way.
-
D.
hasNotableSurfer
Indicates that an entity is associated with a surfer who is recognized as notable or distinguished in some way.
-
E.
notableRiderType
chosen
Indicates that an entity is notably associated with a particular type or category of rider (e.g., cyclist, jockey, driver).
- 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_69e2ff254570819093d197b1900305ac |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:02 a.m.