Triple
T23585635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USF2000 Championship |
E582334
|
entity |
| Predicate | roleInLadder |
P114265
|
FINISHED |
| Object | entry-level step toward IndyCar |
—
|
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: entry-level step toward IndyCar | Statement: [USF2000 Championship, roleInLadder, entry-level step toward IndyCar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInLadder Context triple: [USF2000 Championship, roleInLadder, entry-level step toward IndyCar]
-
A.
roleInRanking
Indicates that an entity holds a specific position or function within a particular ranking or ordered list.
-
B.
roleInClub
Indicates that an entity holds a specific position or function within a particular club.
-
C.
leagueSystemRole
chosen
Indicates the specific role or function an entity holds within a league’s organizational or competitive system.
-
D.
roleInLap
Indicates the specific function or position an entity holds during a particular lap within a sequence of laps.
-
E.
competitionRole
Indicates that an entity holds a specific role, position, or function within a competitive event or contest.
- 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_69e248f8d8248190acd5aee77f0d1709 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b03030f88190bc325f7b4b0137f0 |
completed | April 29, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:41 p.m.