Triple

T35636899
Position Surface form Disambiguated ID Type / Status
Subject Rally2 E1029743 entity
Predicate homologationAuthority P71574 FINISHED
Object FIA 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 | Statement: [Rally2, homologationAuthority, FIA]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: homologationAuthority
Context triple: [Rally2, homologationAuthority, FIA]
  • A. homologationBody chosen
    Indicates the organization or authority responsible for officially approving or certifying something (such as a product, process, or standard) for compliance or use.
  • B. homologationFor
    Indicates that something is formally approved, certified, or validated for a specific use, standard, or regulatory context.
  • C. homologationRole
    Indicates the role or capacity in which an entity participates in a homologation (formal approval or certification) process.
  • D. homologationBasis
    Indicates the underlying standard, criteria, or reference used as the basis for officially approving or certifying something through homologation.
  • E. homologationRequirement
    Indicates that an entity is subject to a formal approval or certification process that must be completed before it can be legally accepted, used, or marketed.
  • 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_69f76e087bdc8190a4794bf9c0bd7634 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f79f48acec8190a9d5964581a94f6c completed May 3, 2026, 7:17 p.m.
PD Predicate disambiguation batch_69f79e4d885881908a3612e2e75cf84f completed May 3, 2026, 7:13 p.m.
Created at: May 3, 2026, 4:05 p.m.