Triple

T28549014
Position Surface form Disambiguated ID Type / Status
Subject "Let's Celebrate!" E722827 entity
Predicate contractionOf P41477 FINISHED
Object "let us celebrate" 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: "let us celebrate" | Statement: ["Let's Celebrate!", contractionOf, "let us celebrate"]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: contractionOf
Context triple: ["Let's Celebrate!", contractionOf, "let us celebrate"]
  • A. isContractionOf chosen
    Indicates that one term is a shortened or combined form derived from another, more complete expression.
  • B. containsContraction
    Indicates that one element includes or is composed of a shortened form created by combining two words and omitting one or more letters (a contraction).
  • C. contractedTo
    Indicates that one entity is formally bound by a contract to provide services, work, or obligations to another entity.
  • D. conjugate
    Indicates that one entity is a grammatical or mathematical counterpart of another, linked by a specific transformation such as verb inflection or complex-number pairing.
  • E. canBeContractedOutOf
    Indicates that a right, obligation, or condition may be removed, waived, or excluded through a contractual agreement between the parties.
  • 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_69f01a60204481909af1bb76247b8221 completed April 28, 2026, 2:24 a.m.
NER Named-entity recognition batch_69f7b5ccbda481908fe1945c35e36ce8 completed May 3, 2026, 8:53 p.m.
PD Predicate disambiguation batch_69f7b4c06f5881908f0b98cad6796478 completed May 3, 2026, 8:49 p.m.
Created at: April 28, 2026, 3:41 a.m.