Triple
T23623663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMD Motorsports |
E583396
|
entity |
| Predicate | competesInCategory |
P53839
|
FINISHED |
| Object | junior formula series |
—
|
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: junior formula series | Statement: [HMD Motorsports, competesInCategory, junior formula series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competesInCategory Context triple: [HMD Motorsports, competesInCategory, junior formula series]
-
A.
hasCompetitionCategory
chosen
Indicates that an entity is associated with a specific category or division within a competition.
-
B.
competeIn
Indicates that an entity takes part as a contender in a particular event, activity, or domain where performance is compared against others.
-
C.
tieneCompetenciaEn
Indicates that an entity possesses skill, expertise, or competence in a specific area, field, or activity.
-
D.
hasCompetition
Indicates that one entity is in a state of rivalry or contest with another entity, typically competing for the same goal, resource, or advantage.
-
E.
competedInDiscipline
Indicates that an entity took part in a competition or event within a specific discipline or category.
- 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_69e248fc8d74819091bd5baef2f36f6f |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b17be6288190a409df700c1003bd |
completed | April 29, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69f118d0e0588190a86527a7747c5427 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:46 p.m.