Triple

T25893371
Position Surface form Disambiguated ID Type / Status
Subject New Orleans Voodoo E652394 entity
Predicate hasImportantLocation P3858 FINISHED
Object St. Louis Cemetery No. 1 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: St. Louis Cemetery No. 1 | Statement: [New Orleans Voodoo, hasImportantLocation, St. Louis Cemetery No. 1]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasImportantLocation
Context triple: [New Orleans Voodoo, hasImportantLocation, St. Louis Cemetery No. 1]
  • A. hasMajorLocation
    Indicates that an entity is primarily situated in, based in, or most significantly associated with a particular location.
  • B. hasLocationRole
    Indicates that an entity holds or plays a specific role in relation to a particular location (e.g., origin, destination, storage site, or operational area).
  • C. notableLocation chosen
    Indicates that a location is especially significant, prominent, or noteworthy in relation to the subject.
  • D. hasProminentLocation
    Indicates that an entity occupies a highly visible, central, or otherwise notable position within a given space or context.
  • E. hasBuildingLocation
    Indicates that a building is situated at, or associated with, a specific geographic or spatial location.
  • 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_69e7ab3c6cc081908de59bfcc28ec19d completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69f621fcea1481909b6f8b3af1ee6820 completed May 2, 2026, 4:10 p.m.
PD Predicate disambiguation batch_69f620dc38088190b56b2b15ed75b3c2 completed May 2, 2026, 4:05 p.m.
Created at: April 22, 2026, 8:22 a.m.