Triple

T24791696
Position Surface form Disambiguated ID Type / Status
Subject GT Daytona E620267 entity
Predicate driverClassificationSystem P6736 FINISHED
Object FIA driver ratings 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 driver ratings | Statement: [GT Daytona, driverClassificationSystem, FIA driver ratings]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: driverClassificationSystem
Context triple: [GT Daytona, driverClassificationSystem, FIA driver ratings]
  • A. classificationSystemBasedOn
    Indicates that one classification system is organized, defined, or derived using another classification system as its basis or reference framework.
  • B. classificationSystem chosen
    Indicates a relationship where an entity is organized or categorized according to a particular classification scheme or taxonomy.
  • C. driveType
    Indicates the type or configuration of the drive mechanism used to power or propel an entity.
  • D. coachType
    Indicates the specific category or role of a coach associated with an entity (e.g., head coach, assistant coach, position coach).
  • E. intendedVehicleClass
    Indicates that one entity is designed or specified to be used with, or is appropriate for, a particular class or category of vehicle.
  • 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_69e2fabe77c8819085f7ce6486248139 completed April 18, 2026, 3:30 a.m.
NER Named-entity recognition batch_69f42d9000b8819081ea2605f3c193d6 completed May 1, 2026, 4:35 a.m.
PD Predicate disambiguation batch_69f420f471a0819095a6cd24ed8f7476 completed May 1, 2026, 3:41 a.m.
Created at: April 18, 2026, 4:47 a.m.