Triple
T38355777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Hillclimb Championship 1938 |
E1046322
|
entity |
| Predicate | hadCompetitorType |
P190800
|
FINISHED |
| Object | top drivers |
—
|
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: top drivers | Statement: [European Hillclimb Championship 1938, hadCompetitorType, top drivers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadCompetitorType Context triple: [European Hillclimb Championship 1938, hadCompetitorType, top drivers]
-
A.
hadCompetitor
Indicates that one entity was in a competitive relationship with another entity, typically operating in the same domain or market.
-
B.
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.
-
C.
competedAs
Indicates that an entity participated in a competition or contest in the role, category, or capacity specified by another entity.
-
D.
tieneCompetencia
Indicates that one entity has or faces competition from another entity.
-
E.
tieneCompetenciaEn
Indicates that an entity possesses skill, expertise, or competence in a specific area, field, or activity.
- 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_69f76e3a94fc81908edc175e8d259e80 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
| PDg | Predicate description generation | batch_69fcd148e6d4819082c118832ecc599b |
completed | May 7, 2026, 5:52 p.m. |
Created at: May 3, 2026, 4:31 p.m.