Triple

T4509603
Position Surface form Disambiguated ID Type / Status
Subject Coronation Cup E102015 entity
Predicate hasHandicap P49216 FINISHED
Object no 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 | Statement: [Coronation Cup, hasHandicap, no]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHandicap
Context triple: [Coronation Cup, hasHandicap, no]
  • A. handicap chosen
    Indicates that one entity imposes or experiences a disadvantage, constraint, or limiting condition in relation to another entity or context.
  • B. hasAdvantage
    Indicates that one entity possesses a benefit, edge, or favorable position over another in a given context.
  • C. hasRuku
    Indicates that an entity performs, contains, or is associated with a ruku (the bowing posture/section) within a prayer or recitation structure.
  • D. handColor
    Indicates that one entity has a specified color associated with its hand or hands.
  • E. hasCoursePar
    Indicates that one course is a parent or higher-level course in relation to another course, such as a prerequisite or overarching course.
  • 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_69bd43d6251c81909deecce3e6e9d69c completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd571138b88190b68bbfc4300aaf9d completed March 20, 2026, 2:17 p.m.
PD Predicate disambiguation batch_69bd5218afb4819087c99e0a1f22e137 completed March 20, 2026, 1:56 p.m.
Created at: March 20, 2026, 1:01 p.m.