Triple
T32655406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aston Martin Racing |
E834846
|
entity |
| Predicate | customerSupport |
P174771
|
FINISHED |
| Object | provides cars to privateer 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: provides cars to privateer teams | Statement: [Aston Martin Racing, customerSupport, provides cars to privateer teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: customerSupport Context triple: [Aston Martin Racing, customerSupport, provides cars to privateer teams]
-
A.
supportStudioCountry
Indicates that a country provides support or backing to a particular studio.
-
B.
digitalSupport
Indicates that one entity provides assistance, resources, or services to another through digital or online means.
-
C.
typeOfSupport
Indicates the kind or category of assistance, help, or backing provided in a given context.
-
D.
supportPolicy
Indicates that one entity endorses, backs, or helps to maintain a particular policy or course of action.
-
E.
supportBase
Indicates that one entity serves as a foundational or backing structure that physically or functionally supports another entity.
- F. None of above. chosen
Provenance (4 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_69f3492f72248190ba42fa596aea50e1 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c7e32ec08190b74856937c4a9fc3 |
completed | May 3, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c77500a08190b2bdeca33bd2ac08 |
completed | May 3, 2026, 3:56 a.m. |
Created at: May 1, 2026, 1:08 a.m.