Triple

T24902943
Position Surface form Disambiguated ID Type / Status
Subject ITF Pace Category 3 (medium) E623627 entity
Predicate hasTypeOfParameter P125616 FINISHED
Object ball-surface interaction 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: ball-surface interaction | Statement: [ITF Pace Category 3 (medium), hasTypeOfParameter, ball-surface interaction]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTypeOfParameter
Context triple: [ITF Pace Category 3 (medium), hasTypeOfParameter, ball-surface interaction]
  • A. hasParameterType chosen
    Indicates that a parameter in a function, method, or operation is associated with a specific data type.
  • B. hasTypeOfReference
    Indicates that one entity uses or is associated with a particular kind or category of reference (such as a citation, pointer, or referential link) to another entity.
  • C. hasParType
    Indicates that an entity has a specific parent type or category to which it belongs.
  • D. hasTypeOfField
    Indicates that an entity possesses or is associated with a specific category or kind of field.
  • E. hasParameter
    Indicates that an entity is associated with a specific parameter that defines or constrains some aspect of its behavior, configuration, or characteristics.
  • 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_69e2fac797cc8190b30d77f4121099ac completed April 18, 2026, 3:30 a.m.
NER Named-entity recognition batch_69f650c70d7c819093d9a0f005f7c8d5 completed May 2, 2026, 7:30 p.m.
PD Predicate disambiguation batch_69f64cab1f648190a2a9460690d18a37 completed May 2, 2026, 7:12 p.m.
Created at: April 18, 2026, 5:27 a.m.