Triple

T10004338
Position Surface form Disambiguated ID Type / Status
Subject City Series E198204 entity
Predicate includesVenueType P10640 FINISHED
Object college basketball arenas 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: college basketball arenas | Statement: [City Series, includesVenueType, college basketball arenas]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: includesVenueType
Context triple: [City Series, includesVenueType, college basketball arenas]
  • A. refersToVenueType chosen
    Indicates that one entity specifies or identifies the type or category of venue associated with another entity.
  • B. home venue type
    Indicates the kind or category of place that serves as the primary location where an entity regularly hosts its events or activities.
  • C. usesVenues
    Indicates that one entity makes use of or operates within specific venues or locations to carry out its activities or services.
  • D. typicalVenues
    Indicates that the specified locations are common or standard places where the associated activity, event, or entity usually occurs or is hosted.
  • E. includesResortType
    Indicates that one entity contains or offers a specific type or category of resort as part of its overall composition or services.
  • 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_69ca830fcca48190bbbd9b20c233835f completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cdcd141ec08190b857fe7e15a8df93 completed April 2, 2026, 1:57 a.m.
PD Predicate disambiguation batch_69cd1da2cf9081908a6c0eb5247d0bc2 completed April 1, 2026, 1:29 p.m.
Created at: March 30, 2026, 8:51 p.m.