Triple
T35740187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford Australia |
E1033011
|
entity |
| Predicate | motorsportRival |
P183878
|
FINISHED |
| Object | Holden Racing Team |
—
|
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: Holden Racing Team | Statement: [Ford Australia, motorsportRival, Holden Racing Team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: motorsportRival Context triple: [Ford Australia, motorsportRival, Holden Racing Team]
-
A.
LeMansCar
Indicates that something is a car designed, built, or used for participation in the 24 Hours of Le Mans endurance race.
-
B.
racingModel
Indicates that one entity is a specific model or version designed or configured for racing in relation to another entity.
-
C.
featuresRaceBetween
Indicates that an event or context includes or showcases a competitive race occurring between participants.
-
D.
raceComponent
Indicates that one entity is a constituent part, segment, or stage within a larger race or racing event involving another entity.
-
E.
raceTrack
Indicates that one entity serves as a race track or racing course used by another entity for racing activities.
- 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_69f76e119d508190a3873cb302063832 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
| PDg | Predicate description generation | batch_69f7a34e80dc8190980d5b7b0b91341d |
completed | May 3, 2026, 7:34 p.m. |
Created at: May 3, 2026, 4:06 p.m.