Triple

T36147345
Position Surface form Disambiguated ID Type / Status
Subject FEI Driving E1045486 entity
Predicate hasIndividualFormat P23479 FINISHED
Object individual drivers 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: individual drivers | Statement: [FEI Driving, hasIndividualFormat, individual drivers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasIndividualFormat
Context triple: [FEI Driving, hasIndividualFormat, individual drivers]
  • A. hasShowFormat
    Indicates that something (such as a show or program) is associated with or presented in a particular format or style.
  • B. hasFormatElement chosen
    Indicates that one entity includes, is composed of, or is associated with a specific structural or formatting component of its overall format.
  • C. hasSecondaryFormat
    Indicates that an entity is associated with an additional, alternative, or supplementary format beyond its primary format.
  • D. hasFormatSpecification
    Indicates that something is associated with a particular format definition or specification that describes how it should be structured or represented.
  • E. containsFormat
    Indicates that one entity includes or is associated with a particular format type as part of its content or representation.
  • 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_69f76e37ace88190a906b107d388f5d1 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_6a00a2f0d1588190a936ea7df0ef0464 completed May 10, 2026, 3:23 p.m.
PD Predicate disambiguation batch_6a00a28ccd94819085b5e123f5a4769e completed May 10, 2026, 3:21 p.m.
Created at: May 3, 2026, 4:08 p.m.