Triple

T13778973
Position Surface form Disambiguated ID Type / Status
Subject IPC Swimming World Championships E331085 entity
Predicate hasWorldRecordsRecognized P110918 FINISHED
Object yes 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: yes | Statement: [IPC Swimming World Championships, hasWorldRecordsRecognized, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasWorldRecordsRecognized
Context triple: [IPC Swimming World Championships, hasWorldRecordsRecognized, yes]
  • A. hasWorldRecordCategory
    Indicates that an entity holding a world record is associated with a specific category or type of record.
  • B. setWorldRecordsIn
    Indicates that an entity has achieved and holds world record performances in a specified domain, event, or location.
  • C. wasWorldRecordFor
    Indicates that something held the status of being the best performance or highest achievement ever recorded for a particular event, category, or metric at a given time.
  • D. worldRecordSet
    Indicates that an entity has achieved and established the best performance ever recorded in the world for a particular activity, event, or measurable criterion.
  • E. hasNotableRecordHolders
    Indicates that an entity is associated with specific individuals or groups recognized for holding notable records related to it.
  • 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_69d81c583b0081909e408a17db517a21 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de0239cbfc81909064ac2457fdfff5 completed April 14, 2026, 9 a.m.
PD Predicate disambiguation batch_69dbbe97846c819093b00ea117b64e0d completed April 12, 2026, 3:47 p.m.
PDg Predicate description generation batch_69dbc59db0148190bcaf9646403ca64f completed April 12, 2026, 4:17 p.m.
Created at: April 9, 2026, 10:11 p.m.