Triple

T6850838
Position Surface form Disambiguated ID Type / Status
Subject Formula 2 Championship E158009 entity
Predicate carNumbering P19365 FINISHED
Object team-based numbering system 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: team-based numbering system | Statement: [Formula 2 Championship, carNumbering, team-based numbering system]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: carNumbering
Context triple: [Formula 2 Championship, carNumbering, team-based numbering system]
  • A. registrationNumber
    Indicates the unique identifier assigned to an entity as part of an official or formal registration process.
  • B. typicalCarNumberRange
    Indicates the usual or commonly expected numerical range of cars associated with an entity (such as a location, time period, or context).
  • C. vehicleRegistrationCode
    Indicates the official registration identifier assigned to a vehicle, typically used for legal identification and record-keeping.
  • D. frontNumbering chosen
    Indicates that an entity is assigned a numbering or label that appears at the front or beginning of something (e.g., a sequence, document, or list).
  • E. RVNumberRange
    Indicates that a recreational vehicle’s number or identifier falls within a specified numeric range.
  • 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_69c6882fae988190864cbba788c5ebb4 completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d84c45708190918adfc028252400 completed March 27, 2026, 7:19 p.m.
PD Predicate disambiguation batch_69c6d0a12834819097d7e6c0b823745e completed March 27, 2026, 6:46 p.m.
Created at: March 27, 2026, 2:20 p.m.