Triple
T5908806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brickyard 400 |
E131408
|
entity |
| Predicate | hasGrandPrize |
P66873
|
FINISHED |
| Object | large purse compared to other NASCAR races |
—
|
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: large purse compared to other NASCAR races | Statement: [Brickyard 400, hasGrandPrize, large purse compared to other NASCAR races]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGrandPrize Context triple: [Brickyard 400, hasGrandPrize, large purse compared to other NASCAR races]
-
A.
hasAwarded
Indicates that one entity has given or conferred an award to another entity.
-
B.
winnerReceives
Indicates that the entity identified as the winner is granted or awarded the specified item, benefit, or outcome as a result of winning.
-
C.
hasAwardItem
Indicates that an entity possesses, is associated with, or has been granted a specific award item.
-
D.
hasAwardConnection
Indicates a relationship where an entity is connected to an award, such as by receiving, being nominated for, or otherwise associated with that award.
-
E.
hasWinnerEngraved
Indicates that the winner of a competition, event, or award is permanently recorded or inscribed on an associated object or medium.
- F. None of above. chosen
Provenance (4 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_69c008593a44819081a07ae0efe6c574 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03ee10b308190afe38b904ae7c5f7 |
completed | March 22, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69c0334fcf6481908e8e74105de9d49b |
completed | March 22, 2026, 6:22 p.m. |
| PDg | Predicate description generation | batch_69c03edf98b881908e9dbc03d3fd6218 |
completed | March 22, 2026, 7:11 p.m. |
Created at: March 22, 2026, 3:59 p.m.