Triple
T35330465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Superstar Racing Experience |
E1020301
|
entity |
| Predicate | raceFormatFeature |
P120070
|
FINISHED |
| Object | heat 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: heat races | Statement: [Superstar Racing Experience, raceFormatFeature, heat races]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raceFormatFeature Context triple: [Superstar Racing Experience, raceFormatFeature, heat races]
-
A.
competitionFormat
Indicates the specific structure or ruleset under which a competition is organized and conducted.
-
B.
tourFormat
Indicates the specific structure, style, or type of a tour associated with an entity.
-
C.
playedFormat
Indicates that an entity (such as a game, show, or media content) is or was presented, delivered, or experienced in a particular format (such as digital, physical, live, or specific media type).
-
D.
hasRaceFormat
chosen
Indicates that an entity is associated with, or characterized by, a particular race format or type of race structure.
-
E.
raceFeatured
Indicates that a particular race or racing event is prominently highlighted or given special attention within a context, such as a program, schedule, or media coverage.
- 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_69f76deacf4481908e7735a5a7715b0a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.