Triple
T35331976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penske Racing |
E1020345
|
entity |
| Predicate | competitions |
P69422
|
FINISHED |
| Object | IndyCar Series |
—
|
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: IndyCar Series | Statement: [Penske Racing, competitions, IndyCar Series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competitions Context triple: [Penske Racing, competitions, IndyCar Series]
-
A.
competitionOf
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
-
B.
competitionFrom
Indicates that one entity is experiencing competitive pressure or rivalry originating from another entity.
-
C.
competitionSeries
chosen
Indicates that one entity is a recurring competitive event or series in which the other entity participates or is featured.
-
D.
competencia
Indicates that one entity is in a state of competition or rivalry with another, typically striving to achieve a similar goal or advantage.
-
E.
competitionUse
Indicates that one entity uses or engages in a competition involving another entity.
- 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_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:03 p.m.