Triple
T19999246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Street Outlaws |
E494273
|
entity |
| Predicate | featuresCompetitionFormat |
P2673
|
FINISHED |
| Object | list-based ranking of racers |
—
|
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: list-based ranking of racers | Statement: [Street Outlaws, featuresCompetitionFormat, list-based ranking of racers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresCompetitionFormat Context triple: [Street Outlaws, featuresCompetitionFormat, list-based ranking of racers]
-
A.
competitionFormat
chosen
Indicates the specific structure or ruleset under which a competition is organized and conducted.
-
B.
featuresCompetitionIn
Indicates that something includes or presents a particular competition as part of its content or structure.
-
C.
appliesToCompetitionFormat
Indicates that something is relevant or specifically designed for a particular competition format.
-
D.
tourFormat
Indicates the specific structure, style, or type of a tour associated with an entity.
-
E.
affectedCompetitionFormat
Indicates that one entity caused a change or influence on the structure, rules, or format of a competition.
- 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e661a09bdc819083305b08a11c6e34 |
completed | April 20, 2026, 5:25 p.m. |
| PD | Predicate disambiguation | batch_69e537fd311881908448f2aea8b4812e |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 11, 2026, 3:32 p.m.