Triple

T24780532
Position Surface form Disambiguated ID Type / Status
Subject Gold Room E619982 entity
Predicate hasInUniverseUse P130421 FINISHED
Object venue for dances and parties 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: venue for dances and parties | Statement: [Gold Room, hasInUniverseUse, venue for dances and parties]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasInUniverseUse
Context triple: [Gold Room, hasInUniverseUse, venue for dances and parties]
  • A. inUniverseUse chosen
    Indicates that something is used or occurs within a particular fictional or conceptual universe, as opposed to in the real world or another setting.
  • B. inUniverseUseRestriction
    Indicates that the use of something is restricted or limited within a specific fictional or defined universe or setting.
  • C. areUsedIn
    Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
  • D. hasFictionalUniverseElement
    Indicates that one entity is a component, feature, or constituent part of the fictional universe represented by the other entity.
  • E. hasInUniverseFormat
    Indicates that something is presented or expressed in a specific format as it exists within a particular fictional or conceptual universe.
  • 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_69e2fabdbe8c8190adbb9434b8636cad completed April 18, 2026, 3:30 a.m.
NER Named-entity recognition batch_69f47b865df48190bf4b6d3e9f9305e6 completed May 1, 2026, 10:08 a.m.
PD Predicate disambiguation batch_69f4682c8a3c8190adbfaac99474eaaf completed May 1, 2026, 8:45 a.m.
Created at: April 18, 2026, 4:44 a.m.