Triple
T21153789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hudson Motor Car Company |
E521259
|
entity |
| Predicate | hadRacingInvolvement |
P8241
|
FINISHED |
| Object | stock car racing |
—
|
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: stock car racing | Statement: [Hudson Motor Car Company, hadRacingInvolvement, stock car racing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadRacingInvolvement Context triple: [Hudson Motor Car Company, hadRacingInvolvement, stock car racing]
-
A.
hasMotorsportInvolvement
chosen
Indicates that an entity is involved in motorsport, such as through participation, organization, sponsorship, or other direct association with motor racing activities.
-
B.
hasRacingUseSince
Indicates that an entity has been used for racing starting from a specified point in time.
-
C.
racedIn
Indicates that an entity participated as a competitor in a particular race or racing event.
-
D.
hadGrandPrix
Indicates that a particular Grand Prix event took place as part of, or was hosted by, a given competition, season, or venue.
-
E.
hasDrivenInCategory
Indicates that an entity has previously driven or operated a vehicle within a specified driving category or classification.
- 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_69e0b50d1ea481909c07e63c3ead9316 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7252929748190afd85be40294293f |
completed | April 21, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f5f8a5bc819081918c7fa8e4496d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:58 p.m.