Triple

T36390869
Position Surface form Disambiguated ID Type / Status
Subject Premier Handicap E896322 entity
Predicate weightVariationReason P34734 FINISHED
Object differences in perceived ability of horses 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: differences in perceived ability of horses | Statement: [Premier Handicap, weightVariationReason, differences in perceived ability of horses]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: weightVariationReason
Context triple: [Premier Handicap, weightVariationReason, differences in perceived ability of horses]
  • A. weightCondition
    Indicates that a specified weight-related requirement or constraint holds between entities or values.
  • B. weightIssue
    Indicates that there is a problem, concern, or abnormal condition related to the weight of an entity.
  • C. weightStandardInfluencedBy chosen
    Indicates that a weight standard is affected, shaped, or determined by another factor, standard, or influence.
  • D. weight
    Indicates a relationship where a numerical value quantifies how heavy an entity is, often used to measure or compare mass or load.
  • E. intendedWeight
    Indicates the target or desired weight that an entity is meant or planned to have, rather than its current actual weight.
  • 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_69f76e52e3108190becf70b090ae7bd6 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7c371931c8190afb1d4dd5157f92c completed May 3, 2026, 9:51 p.m.
PD Predicate disambiguation batch_69f7c1b91fd88190ab85afd626603769 completed May 3, 2026, 9:44 p.m.
Created at: May 3, 2026, 4:10 p.m.