Triple

T33951410
Position Surface form Disambiguated ID Type / Status
Subject women's 100 metres hurdles E870449 entity
Predicate commonIndoorEquivalent P145007 FINISHED
Object women's 60 metres hurdles 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: women's 60 metres hurdles | Statement: [women's 100 metres hurdles, commonIndoorEquivalent, women's 60 metres hurdles]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: commonIndoorEquivalent
Context triple: [women's 100 metres hurdles, commonIndoorEquivalent, women's 60 metres hurdles]
  • A. hasIndoorCounterpart chosen
    Indicates that something has a corresponding or equivalent version designed for use indoors.
  • B. hasIndoorType
    Indicates that an entity is associated with a specific type or category of indoor environment or indoor feature.
  • C. indoorOutdoorRelation
    Indicates a spatial relationship specifying whether something is located indoors, outdoors, or how it connects indoor and outdoor spaces.
  • D. indoorSectionName
    Indicates the specific named section or area within an indoor space to which an entity is related.
  • E. indoorAdvantage
    Indicates that an entity has a beneficial edge or improved performance when conditions or activities occur indoors rather than outdoors.
  • 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_69f3499c2d7481909c953a5010227725 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69fe9b0276d48190b554fa22b043e6d8 completed May 9, 2026, 2:25 a.m.
PD Predicate disambiguation batch_69fe999692b081909921e1148d66f0ef completed May 9, 2026, 2:19 a.m.
Created at: May 1, 2026, 1:49 a.m.