Triple
T24976892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TI–Raleigh |
E625045
|
entity |
| Predicate | hadNotableRider |
P158699
|
FINISHED |
| Object | Cees Priem |
—
|
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: Cees Priem | Statement: [TI–Raleigh, hadNotableRider, Cees Priem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadNotableRider Context triple: [TI–Raleigh, hadNotableRider, Cees Priem]
-
A.
hadNotableRider
chosen
Indicates that an animal, vehicle, or conveyance was ridden by a person considered historically or culturally notable.
-
B.
hasNotableRide
Indicates that an entity is associated with a particularly remarkable or well-known ride or attraction.
-
C.
hasNotableJockey
Indicates that an entity (typically a racehorse) is or was ridden by a jockey who is considered notable or distinguished.
-
D.
hasNotableHorse
Indicates that an entity is associated with a horse that is considered notable or distinguished in some recognized way.
-
E.
hasNotableSurfer
Indicates that an entity is associated with a surfer who is recognized as notable or distinguished in some way.
- 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_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 18, 2026, 6:02 a.m.