Triple

T25556612
Position Surface form Disambiguated ID Type / Status
Subject Money in the Bank ladder match E640588 entity
Predicate timeLimitForContract P67217 FINISHED
Object one year 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: one year | Statement: [Money in the Bank ladder match, timeLimitForContract, one year]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: timeLimitForContract
Context triple: [Money in the Bank ladder match, timeLimitForContract, one year]
  • A. timeLimited
    Indicates that the relationship or action is constrained to occur or remain valid only within a specific, limited time period.
  • B. signedContractLength chosen
    Indicates the duration or term length specified in a contract that has been formally signed between parties.
  • C. timeLimitForRatification
    Indicates the deadline or maximum period allowed for an agreement, decision, or act to be formally ratified.
  • D. timeBetweenAnnouncementAndTermination
    Indicates the duration of time that elapses between when something is officially announced and when it is subsequently terminated.
  • E. timeoutDuration
    Indicates the length of time that may elapse before an operation, request, or session is automatically terminated or considered failed.
  • 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_69e75dc101a881909fd33b02174e9768 completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f5f8ca2cf48190997cd68875571217 completed May 2, 2026, 1:14 p.m.
PD Predicate disambiguation batch_69f468421ba08190880eac99135e5970 completed May 1, 2026, 8:45 a.m.
Created at: April 21, 2026, 3:40 p.m.