Triple

T2781933
Position Surface form Disambiguated ID Type / Status
Subject St. Louis Arena E61715 entity
Predicate siteUseAfterDemolition P43161 FINISHED
Object commercial development 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: commercial development | Statement: [St. Louis Arena, siteUseAfterDemolition, commercial development]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: siteUseAfterDemolition
Context triple: [St. Louis Arena, siteUseAfterDemolition, commercial development]
  • A. demolishedWith
    Indicates that one entity was destroyed or torn down using another specified tool, method, or agent.
  • B. hasDemolitionOrDestruction
    Indicates that one entity causes, undergoes, or is associated with the demolition or destruction of another entity.
  • C. demolishedOriginalStructures
    Indicates that one entity has completely destroyed or removed the original structures associated with another entity.
  • D. demolished
    Indicates that one entity completely destroyed or razed another entity, typically a structure or object, so that it no longer exists in its previous form.
  • E. demolishedToMakeWayFor
    Indicates that one entity was intentionally destroyed or removed in order to create space for another entity or development.
  • 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_69ab4b7e43c48190997b8fc8fb1663ab completed March 6, 2026, 9:47 p.m.
NER Named-entity recognition batch_69abddceb9d88190961e30d521a21552 completed March 7, 2026, 8:11 a.m.
PD Predicate disambiguation batch_69abdd00b65c8190a8ea444308c4fa2b completed March 7, 2026, 8:08 a.m.
PDg Predicate description generation batch_69abddcc348081908b5f760899389d4f completed March 7, 2026, 8:11 a.m.
Created at: March 6, 2026, 9:57 p.m.