Triple

T33699024
Position Surface form Disambiguated ID Type / Status
Subject Alexandria, Colony of Virginia E863399 entity
Predicate hadUrbanFeature P1495 FINISHED
Object wharves 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: wharves | Statement: [Alexandria, Colony of Virginia, hadUrbanFeature, wharves]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hadUrbanFeature
Context triple: [Alexandria, Colony of Virginia, hadUrbanFeature, wharves]
  • A. hasUrbanFeature chosen
    Indicates that a place or area possesses a specific urban element or infrastructure feature (such as roads, parks, or buildings) as part of its built environment.
  • B. hasUrbanFunction
    Indicates that an entity serves a specific role or purpose within an urban context, such as providing services, infrastructure, or activities typical of a city environment.
  • C. hasUrbanFabric
    Indicates that one entity possesses, contains, or is characterized by a particular pattern or structure of built-up urban development.
  • D. hasUrbanAreaCharacter
    Indicates that something possesses qualities, features, or conditions typical of an urban area.
  • E. hasUrbanSectionsIn
    Indicates that an entity includes or contains sections that are classified as urban within a specified area or region.
  • 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_69f3498723a08190ac034339cc78eade completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6fa8bd50481908fd1a9b5406a5855 completed May 3, 2026, 7:34 a.m.
PD Predicate disambiguation batch_69f6f96dd4c8819093d6a7bd046a9ad5 completed May 3, 2026, 7:29 a.m.
Created at: May 1, 2026, 1:43 a.m.