Triple

T24206598
Position Surface form Disambiguated ID Type / Status
Subject Mark St. John E600420 entity
Predicate reasonForLimitedTouringWithKiss P126138 FINISHED
Object suffered from Reiter's syndrome 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: suffered from Reiter's syndrome | Statement: [Mark St. John, reasonForLimitedTouringWithKiss, suffered from Reiter's syndrome]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reasonForLimitedTouringWithKiss
Context triple: [Mark St. John, reasonForLimitedTouringWithKiss, suffered from Reiter's syndrome]
  • A. hasTourismRestriction
    Indicates that there is a limitation, prohibition, or special condition affecting tourism-related activities or access in relation to the referenced entity.
  • B. hasCoSanctionedTour
    Indicates that two or more entities jointly authorize, support, or participate in the same tour or touring event.
  • C. eligibilityRestrictedBy chosen
    Indicates that an entity’s eligibility for something is limited, constrained, or conditioned by another specified factor or rule.
  • D. hadRestrictionsOn
    Indicates that one entity imposed or was subject to specific limitations, rules, or constraints regarding another entity or activity.
  • E. touringScope
    Indicates the extent or range of locations, venues, or areas covered by an entity’s tour or touring activity.
  • 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_69e2953344c48190875730c7d52112a0 completed April 17, 2026, 8:16 p.m.
NER Named-entity recognition batch_69f27ca63d188190add6c41929bb5cb5 completed April 29, 2026, 9:48 p.m.
PD Predicate disambiguation batch_69f1c43e55688190b55fc20274ed471c completed April 29, 2026, 8:41 a.m.
Created at: April 17, 2026, 11:42 p.m.