Triple
T35564244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2009 Lenox Industrial Tools 301 |
E1027723
|
entity |
| Predicate | raceNameSponsor |
P15097
|
FINISHED |
| Object | Lenox Industrial Tools |
—
|
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: Lenox Industrial Tools | Statement: [2009 Lenox Industrial Tools 301, raceNameSponsor, Lenox Industrial Tools]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raceNameSponsor Context triple: [2009 Lenox Industrial Tools 301, raceNameSponsor, Lenox Industrial Tools]
-
A.
raceName
Indicates the specific race or competition designation associated with an entity or event.
-
B.
sponsorshipName
chosen
Indicates the name or title associated with a sponsorship relationship between entities.
-
C.
sponsorshipBrand
Indicates that one entity serves as a sponsoring brand for another entity, typically providing support, funding, or endorsement.
-
D.
prizeSponsor
Indicates that an entity provides financial or material support as the sponsor of a particular prize or award.
-
E.
raceNamedAfterIsRunAt
Indicates that a race, whose name references a particular place or venue, is actually held or conducted at that same location.
- 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_69f76e020fd8819081cb080e7e203083 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79a54aa3c8190b2bb5d790b2d42d4 |
completed | May 3, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69f7961970408190b669cc556e30a608 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.