Triple

T2630199
Position Surface form Disambiguated ID Type / Status
Subject Chatr Mobile E59613 entity
Predicate contractRequirement P15887 FINISHED
Object no long-term contract 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: no long-term contract | Statement: [Chatr Mobile, contractRequirement, no long-term contract]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: contractRequirement
Context triple: [Chatr Mobile, contractRequirement, no long-term contract]
  • A. communicationRequirement
    Indicates that one entity is obligated or expected to communicate with another entity under specified conditions or for a particular purpose.
  • B. evaluationRequirement
    Indicates that one entity imposes or specifies conditions under which another entity must be assessed, tested, or evaluated.
  • C. approvalRequirement
    Indicates that one entity must grant permission or authorization before another entity’s action, decision, or state change can proceed.
  • D. dialogRequirement
    Indicates that a certain condition, piece of information, or interaction must occur within a dialog or conversation for a related action, state, or process to proceed or be considered valid.
  • E. contractFeature chosen
    Indicates that one entity is a feature, term, or provision that is included in or associated with a particular contract.
  • 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_69ab4ac8596c8190b34997e73d9e991c completed March 6, 2026, 9:44 p.m.
NER Named-entity recognition batch_69abdb0e7b888190bfa5d2e33f00ec0f completed March 7, 2026, 8 a.m.
PD Predicate disambiguation batch_69abd810d7f481908e81c305772c4c14 completed March 7, 2026, 7:47 a.m.
Created at: March 6, 2026, 9:50 p.m.