Triple

T31755367
Position Surface form Disambiguated ID Type / Status
Subject Anyone Can Cook E810542 entity
Predicate laterVindicatedBy P162381 FINISHED
Object Remy’s success at Gusteau's 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: Remy’s success at Gusteau's | Statement: [Anyone Can Cook, laterVindicatedBy, Remy’s success at Gusteau's]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: laterVindicatedBy
Context triple: [Anyone Can Cook, laterVindicatedBy, Remy’s success at Gusteau's]
  • A. laterRaised
    Indicates that one entity was raised, elevated, or brought up at a time subsequent to another referenced event or state.
  • B. exoneratedIn chosen
    Indicates that an entity has been officially cleared of blame or legal responsibility in a particular case, situation, or proceeding.
  • C. laterRestored
    Indicates that something previously altered, damaged, or removed was subsequently brought back to its earlier state or condition.
  • D. laterRevertedTo
    Indicates that a prior change, state, or condition was subsequently undone, returning the subject to its earlier form or status.
  • E. laterRepresented
    Indicates that one entity subsequently served as an official representative or agent for another entity at a later time.
  • 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_69f348e340d48190b780fae618c51464 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69ff65987ff88190b09be64f7c0e1da9 completed May 9, 2026, 4:49 p.m.
PD Predicate disambiguation batch_69ff6525b0548190bef7a9f009e00bb8 completed May 9, 2026, 4:47 p.m.
Created at: April 30, 2026, 11:29 p.m.