Triple
T35753383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coppa Acerbo |
E1033374
|
entity |
| Predicate | raceCategories |
P128813
|
FINISHED |
| Object | Grand Prix cars |
—
|
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: Grand Prix cars | Statement: [Coppa Acerbo, raceCategories, Grand Prix cars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raceCategories Context triple: [Coppa Acerbo, raceCategories, Grand Prix cars]
-
A.
raceCategory
Indicates the classification of an entity into a specific race or racial group within a defined categorization system.
-
B.
motorsportClass
chosen
Indicates that one entity is classified as a specific motorsport category or division associated with another entity.
-
C.
raceTypeDetail
Indicates the specific category or classification of a race, providing detailed information about the type of race involved in the relationship.
-
D.
raceComponent
Indicates that one entity is a constituent part, segment, or stage within a larger race or racing event involving another entity.
-
E.
styleOfRacing
Indicates the specific manner or approach in which an entity participates in or performs racing.
- 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a198e24881909cc292e420269a8c |
completed | May 3, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.