Triple

T33951390
Position Surface form Disambiguated ID Type / Status
Subject women's 100 metres hurdles E870449 entity
Predicate previousStandardDistance P128748 FINISHED
Object 80 metres hurdles 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: 80 metres hurdles | Statement: [women's 100 metres hurdles, previousStandardDistance, 80 metres hurdles]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: previousStandardDistance
Context triple: [women's 100 metres hurdles, previousStandardDistance, 80 metres hurdles]
  • A. distanceStandard
    Indicates that a specified distance between entities is measured or evaluated according to a particular standard or reference criterion.
  • B. primaryDistance
    Indicates the main or most significant measure of distance between two entities in the relationship.
  • C. formerDistance chosen
    Indicates that a distance or spatial separation between entities existed in the past but no longer holds in the present.
  • D. distancedFrom
    Indicates that one entity is physically or metaphorically kept at a certain distance or separation from another entity.
  • E. designedForUseDistance
    Indicates that something is intended or optimized to be used at a particular distance from the user or another object.
  • 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_69ff246e0d4481908bcec718e1d4025b completed May 9, 2026, 12:11 p.m.
PD Predicate disambiguation batch_69ff23cb70ac81909b776ace4597ae9c completed May 9, 2026, 12:08 p.m.
Created at: May 1, 2026, 1:49 a.m.