Triple

T26729544
Position Surface form Disambiguated ID Type / Status
Subject Tokyo Racecourse E673927 entity
Predicate hasInfieldAmusementFacilities P187562 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: [Tokyo Racecourse, hasInfieldAmusementFacilities, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasInfieldAmusementFacilities
Context triple: [Tokyo Racecourse, hasInfieldAmusementFacilities, yes]
  • A. amusementParkType
    Indicates that one entity is classified as a specific type or category of amusement park in relation to another entity.
  • B. developedAsAmusementArea
    Indicates that an area was created or transformed specifically for recreational or entertainment purposes.
  • C. hasRailroadAttraction
    Indicates that one entity features or contains a railroad-related attraction, such as a railway exhibit, ride, or point of interest.
  • D. indoorPark
    Indicates that an activity or event takes place in an indoor park or indoor recreational facility.
  • E. hasThemeParkAreaType
    Indicates that an entity is associated with a specific type or category of theme park area.
  • 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_69eecda57ab481909424e98f2835e7d8 completed April 27, 2026, 2:44 a.m.
NER Named-entity recognition batch_69fb6fdc7eb081908ab8475efb38c430 completed May 6, 2026, 4:44 p.m.
PD Predicate disambiguation batch_69fb5a986e588190b7a10892bd2ff44c completed May 6, 2026, 3:13 p.m.
PDg Predicate description generation batch_69fb6fdab95c81909acff3c6a2359787 completed May 6, 2026, 4:44 p.m.
Created at: April 27, 2026, 3:44 a.m.