Triple

T24284597
Position Surface form Disambiguated ID Type / Status
Subject 4 × 100 metres relay E605635 entity
Predicate trackSegment P155685 FINISHED
Object curved legs and straight legs 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: curved legs and straight legs | Statement: [4 × 100 metres relay, trackSegment, curved legs and straight legs]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: trackSegment
Context triple: [4 × 100 metres relay, trackSegment, curved legs and straight legs]
  • A. trackedSegment
    Indicates that a specific segment or portion of something (such as a path, process, or sequence) is being monitored, recorded, or followed over time.
  • B. trackFeature
    Indicates that one entity monitors, records, or follows the behavior, state, or evolution of a particular feature associated with another entity.
  • C. track
    Indicates that one entity follows, monitors, or keeps a record of another entity’s state, behavior, or progress over time.
  • D. transportSegment
    Indicates a distinct portion of a larger journey or route during which something or someone is transported from one point to another.
  • E. trackOver
    Indicates that one entity follows, monitors, or records the behavior, state, or progress of another entity across a period of time or over a sequence of events.
  • 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_69e295480d0c8190846fc3c2e2da1d4c completed April 17, 2026, 8:17 p.m.
NER Named-entity recognition batch_69f28f54c5948190a28207d47d6205e4 completed April 29, 2026, 11:08 p.m.
PD Predicate disambiguation batch_69f1c457a2908190993824395b3c365d completed April 29, 2026, 8:41 a.m.
PDg Predicate description generation batch_69f27a753ca8819095706970d368f762 completed April 29, 2026, 9:39 p.m.
Created at: April 18, 2026, 12:08 a.m.