Triple
T27454412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Attilio Bettega |
E692544
|
entity |
| Predicate | hasCompetitorNumberType |
P135676
|
FINISHED |
| Object | rally car number |
—
|
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: rally car number | Statement: [Attilio Bettega, hasCompetitorNumberType, rally car number]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompetitorNumberType Context triple: [Attilio Bettega, hasCompetitorNumberType, rally car number]
-
A.
hasCompetitorNumber
chosen
Indicates that an entity is associated with a specific competitor identification number used to distinguish it in a competitive context.
-
B.
competitorCount
Indicates the number of competitors associated with a given entity or context.
-
C.
hadCompetitorType
Indicates that an entity had a competitor belonging to a specified type or category.
-
D.
hasCompetitionElement
Indicates that one entity includes, involves, or is associated with a specific competitive component, aspect, or feature.
-
E.
hasTournamentType
Indicates that a tournament is classified as belonging to a specific type or category (e.g., league, knockout, friendly).
- 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_69ef5207903881909427745cda05d27a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69ff0491409c8190be40f633a58da0b1 |
completed | May 9, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69ff040bb5cc81909534c7eee85d5e90 |
completed | May 9, 2026, 9:53 a.m. |
Created at: April 27, 2026, 12:48 p.m.