Triple

T33772164
Position Surface form Disambiguated ID Type / Status
Subject C'est le dernier qui a parlé qui a raison E865407 entity
Predicate performedInFinal P23986 FINISHED
Object yes 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: yes | Statement: [C'est le dernier qui a parlé qui a raison, performedInFinal, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: performedInFinal
Context triple: [C'est le dernier qui a parlé qui a raison, performedInFinal, yes]
  • A. playedInFinals chosen
    Indicates that an entity participated as a competitor or player in the final round of a competition or tournament.
  • B. hasFinale
    Indicates that one entity serves as the concluding or final part (such as an ending segment, episode, or event) of another entity.
  • C. isFinalsOf
    Indicates that one entity represents the final or concluding stage, round, or version of another entity.
  • D. finalFilmPerformanceOf
    Indicates that one entity is the last film performance or role undertaken by the other entity before they stopped acting in films.
  • E. hasFinalRound
    Indicates that an event, process, or competition includes a concluding or decisive final round.
  • 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_69f3498df6f88190bf9647ea4e4a956e completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69fe9b0276d48190b554fa22b043e6d8 completed May 9, 2026, 2:25 a.m.
PD Predicate disambiguation batch_69fe999692b081909921e1148d66f0ef completed May 9, 2026, 2:19 a.m.
Created at: May 1, 2026, 1:45 a.m.