Triple
T22380079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Automobile Racing Club of America |
E553247
|
entity |
| Predicate | typicalRaceCarType |
P121081
|
FINISHED |
| Object | stock car |
—
|
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 | Statement: [Automobile Racing Club of America, typicalRaceCarType, stock car]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRaceCarType Context triple: [Automobile Racing Club of America, typicalRaceCarType, stock car]
-
A.
raceComponent
Indicates that one entity is a constituent part, segment, or stage within a larger race or racing event involving another entity.
-
B.
styleOfRacing
Indicates the specific manner or approach in which an entity participates in or performs racing.
-
C.
raceCategory
Indicates the classification of an entity into a specific race or racial group within a defined categorization system.
-
D.
raceTypeDetail
Indicates the specific category or classification of a race, providing detailed information about the type of race involved in the relationship.
-
E.
appearsAsRacerClass
chosen
Indicates that an entity is presented or functions in the role or category of a racer class within a given context.
- 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_69e11e4c03248190a26a5060ea6973ee |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1582afe6c819093940f9d817c64a8 |
completed | April 29, 2026, 1 a.m. |
| PD | Predicate disambiguation | batch_69e73011e6388190a05edf137f488441 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:45 p.m.