Triple

T3045420
Position Surface form Disambiguated ID Type / Status
Subject Richmond War Memorial E83433 entity
Predicate hasLocationEnvironment P13810 FINISHED
Object urban setting 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: urban setting | Statement: [Richmond War Memorial, hasLocationEnvironment, urban setting]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLocationEnvironment
Context triple: [Richmond War Memorial, hasLocationEnvironment, urban setting]
  • A. hasLocationComponent
    Indicates that something includes, is associated with, or is composed of a specific location-related part or element.
  • B. supportsLocation
    Indicates that one entity provides the necessary structure, foundation, or capacity to hold, host, or accommodate another entity at a particular place or position.
  • C. hasEnvironmentType chosen
    Indicates that an entity is associated with or occurs within a specific type or category of environment.
  • D. hasEnvironmentalFunction
    Indicates that an entity serves a specific role or purpose related to the environment, such as contributing to ecological processes, protection, or sustainability.
  • E. usedInEnvironment
    Indicates that something is utilized or operates within a particular environment or context.
  • 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_69ad8b24924c8190a9bb6f61d519e4ae completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad9b602ed881909a72662eb544866b completed March 8, 2026, 3:53 p.m.
PD Predicate disambiguation batch_69ad961fc62c819087c4c3a44b00847d completed March 8, 2026, 3:30 p.m.
Created at: March 8, 2026, 3:01 p.m.