Triple

T32926287
Position Surface form Disambiguated ID Type / Status
Subject Plutôt mourir que faillir E842280 entity
Predicate shortFormTranslation P83434 FINISHED
Object Rather die than fail 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: Rather die than fail | Statement: [Plutôt mourir que faillir, shortFormTranslation, Rather die than fail]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: shortFormTranslation
Context triple: [Plutôt mourir que faillir, shortFormTranslation, Rather die than fail]
  • A. shortFormLanguage
    Indicates that one entity is a shortened or abbreviated language representation or code corresponding to another language entity.
  • B. shortFormType chosen
    Indicates that one entity is a shortened, abbreviated, or otherwise condensed form or variant of another entity.
  • C. shortFormat
    Indicates that something is presented in a condensed or abbreviated form compared to its full or standard representation.
  • D. abbreviationOrShortForm
    Indicates that one term is an abbreviation or shortened form of another term.
  • E. shortNameInJapanese
    Indicates that an entity has a specific abbreviated or shorter form of its name expressed in the Japanese language.
  • 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_69f34948adfc8190a937f1f622783c0b completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6d0da57ac81908b5fdbd8f44f8249 completed May 3, 2026, 4:36 a.m.
PD Predicate disambiguation batch_69f6cfe5f93c8190995c53dbbe380a32 completed May 3, 2026, 4:32 a.m.
Created at: May 1, 2026, 1:20 a.m.