Triple
T22058934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert Yates Racing |
E545098
|
entity |
| Predicate | suppliedEnginesTo |
P17328
|
FINISHED |
| Object | other Ford NASCAR teams |
—
|
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: other Ford NASCAR teams | Statement: [Robert Yates Racing, suppliedEnginesTo, other Ford NASCAR teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suppliedEnginesTo Context triple: [Robert Yates Racing, suppliedEnginesTo, other Ford NASCAR teams]
-
A.
historicallySuppliedEnginesFor
Indicates that one entity has, in the past, provided engines to another entity, typically as a supplier or manufacturer.
-
B.
engineSupplier
chosen
Indicates a relationship where one entity supplies or provides engines to another entity.
-
C.
numberOfEngines
Indicates the quantity of engines associated with or used by an entity.
-
D.
offeredEngineType
Indicates that a particular type of engine is made available or provided as an option in a given context.
-
E.
suppliesTo
Indicates that one entity provides or delivers goods, services, or resources to 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_69e11e3377c48190890c17407b9527d6 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1285ac9608190ab4f89d4ee7350d0 |
completed | April 28, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69e6f643ca74819083e8ab78e843f243 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:27 p.m.