Triple

T31329102
Position Surface form Disambiguated ID Type / Status
Subject Navigo fare system E798975 entity
Predicate cardPersonalization P113857 FINISHED
Object personalized with holder name and photo for some card types 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: personalized with holder name and photo for some card types | Statement: [Navigo fare system, cardPersonalization, personalized with holder name and photo for some card types]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: cardPersonalization
Context triple: [Navigo fare system, cardPersonalization, personalized with holder name and photo for some card types]
  • A. personalizedCardSupports
    Indicates that a personalized card is compatible with, or can be used in conjunction with, a particular system, service, or feature.
  • B. cardFormat
    Indicates the specific layout or structural style in which a card or card-like item is presented or encoded.
  • C. cardDesignFeature chosen
    Indicates that a card possesses or incorporates a particular design feature or visual element.
  • D. cardVariant
    Indicates that one card is a specific version or variation of another base card.
  • E. physicalCardColor
    Indicates the relationship between a physical card and the color that characterizes its appearance.
  • 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_69f224e3238c8190b2291f50ea4962cd completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f69ede2ea48190999b3d041f7bf55e completed May 3, 2026, 1:03 a.m.
PD Predicate disambiguation batch_69f69d1d25e88190a7f57d323574da90 completed May 3, 2026, 12:55 a.m.
Created at: April 29, 2026, 9:16 p.m.