Triple
T35370515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASCAR K&N Pro Series East |
E1021755
|
entity |
| Predicate | typicalCompetitorProfile |
P206955
|
FINISHED |
| Object | young drivers |
—
|
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: young drivers | Statement: [NASCAR K&N Pro Series East, typicalCompetitorProfile, young drivers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCompetitorProfile Context triple: [NASCAR K&N Pro Series East, typicalCompetitorProfile, young drivers]
-
A.
underlyingCompanyMajorCompetitor
Indicates that one company serves as a primary or significant competitor to another company.
-
B.
rivalCompanyProductType
Indicates that one company's product type is in competition with or serves as a rival to another company's product type.
-
C.
competitorCategory
Indicates that two entities operate in the same competitive category or market segment, positioning them as rivals within that domain.
-
D.
competitorOwner
Indicates that one entity owns or controls a business or asset that competes in the same market or domain as another entity’s business or asset.
-
E.
attractsCompetitorsFrom
Indicates that one entity draws or lures competitors away from another entity or location.
- 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_69f76df000488190ab7c97f565677055 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.