Triple
T32069299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rust-eze Racing |
E818966
|
entity |
| Predicate | rivalSponsors |
P22658
|
FINISHED |
| Object | Dinoco |
—
|
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: Dinoco | Statement: [Rust-eze Racing, rivalSponsors, Dinoco]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rivalSponsors Context triple: [Rust-eze Racing, rivalSponsors, Dinoco]
-
A.
rivalOf
chosen
Indicates a relationship in which two entities compete against or oppose each other, often seeking advantage in the same domain or objective.
-
B.
sponsors
Indicates that one entity provides financial or material support to another, often in exchange for association, promotion, or fulfillment of certain activities or goals.
-
C.
bearerRivalOf
Indicates that the bearer is in a state of rivalry or competitive opposition with the related entity.
-
D.
partnerInCompetition
Indicates that two or more entities are collaborating as partners or teammates within the same competitive event or context.
-
E.
rivalryBasis
Indicates the underlying reason, cause, or grounds on which a rivalry between entities is based.
- 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_69f348fecc088190af1470afe5a969f0 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b522fe4c819093c731ec03756536 |
completed | May 3, 2026, 2:38 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:23 a.m.