Triple
T29447762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LMGTE Pro (historic) |
E746895
|
entity |
| Predicate | allowedDriverRating |
P59739
|
FINISHED |
| Object | FIA Platinum |
—
|
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: FIA Platinum | Statement: [LMGTE Pro (historic), allowedDriverRating, FIA Platinum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowedDriverRating Context triple: [LMGTE Pro (historic), allowedDriverRating, FIA Platinum]
-
A.
typicalDriverRatings
Indicates the usual or average ratings that drivers receive, representing a typical evaluation of their performance.
-
B.
allowsCupDrivers
Indicates that one entity grants permission or authorization for Cup drivers to participate in or make use of another entity.
-
C.
usesRating
Indicates that one entity applies, relies on, or incorporates a rating assigned to another entity.
-
D.
hasRatingLevel
chosen
Indicates that an entity is associated with a particular rating level or score category.
-
E.
regulatesRatingsFor
Indicates that one entity has authority or responsibility to control, set, or enforce the rating standards or criteria applied to another entity.
- 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_69f0a7a230488190b44a97fe3d16f731 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: April 28, 2026, 3:29 p.m.