Triple

T24706579
Position Surface form Disambiguated ID Type / Status
Subject Will Hopoate E611907 entity
Predicate contractedTo P157013 FINISHED
Object St Helens R.F.C. NE NERFINISHED

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: St Helens R.F.C. | Statement: [Will Hopoate, contractedTo, St Helens R.F.C.]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: contractedTo
Context triple: [Will Hopoate, contractedTo, St Helens R.F.C.]
  • A. canBeContractedOutOf
    Indicates that a right, obligation, or condition may be removed, waived, or excluded through a contractual agreement between the parties.
  • 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. isContractionOf
    Indicates that one term is a shortened or combined form derived from another, more complete expression.
  • D. collapsedWith
    Indicates that one entity fell down or caved in together with another entity, typically as part of the same collapse event.
  • E. developmentalContractedWith
    Indicates a formal developmental agreement or contract established between two entities, typically for research, design, or product development activities.
  • F. None of above. chosen

Provenance (4 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_69e2c4d9c24c8190a3712d74327f0c6e completed April 17, 2026, 11:40 p.m.
NER Named-entity recognition batch_69f410fe3b848190ae296a29f742ee30 completed May 1, 2026, 2:33 a.m.
PD Predicate disambiguation batch_69f40ee8ada8819089a7016b50308ff0 completed May 1, 2026, 2:24 a.m.
PDg Predicate description generation batch_69f410fc18808190b4e47d5a71d3a126 completed May 1, 2026, 2:33 a.m.
Created at: April 18, 2026, 3:24 a.m.