Triple

T24577791
Position Surface form Disambiguated ID Type / Status
Subject Greensboro–High Point metropolitan area E608159 entity
Predicate containsConventionCenter P93010 FINISHED
Object Greensboro Coliseum Complex NE NERFINISHED

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: Greensboro Coliseum Complex | Statement: [Greensboro–High Point metropolitan area, containsConventionCenter, Greensboro Coliseum Complex]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: containsConventionCenter
Context triple: [Greensboro–High Point metropolitan area, containsConventionCenter, Greensboro Coliseum Complex]
  • A. hasConventionHalls chosen
    Indicates that an entity possesses or includes one or more convention halls as part of its facilities or infrastructure.
  • B. totalConventionSpace
    Indicates the total amount of convention or conference space associated with an entity.
  • C. venueComplex
    Indicates that one venue is a complex or larger facility that contains or encompasses another venue.
  • D. conventionCity
    Indicates that a city is the location where a particular convention or conference is held.
  • E. hasConferenceSpace
    Indicates that an entity provides or includes dedicated space suitable for holding conferences, meetings, or similar gatherings.
  • 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_69e2c4cdab6c8190aae6e5d3de55c95e completed April 17, 2026, 11:39 p.m.
NER Named-entity recognition batch_69f2a97be2ac8190aecf5e54a37e266a completed April 30, 2026, 12:59 a.m.
PD Predicate disambiguation batch_69f2a6c1f07081908edf0b521767e79b completed April 30, 2026, 12:48 a.m.
Created at: April 18, 2026, 2:29 a.m.