Triple

T6691911
Position Surface form Disambiguated ID Type / Status
Subject Beaumont-Wilshire E152646 entity
Predicate hasNeighborhoodIdentity P72231 FINISHED
Object historic residential character 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: historic residential character | Statement: [Beaumont-Wilshire, hasNeighborhoodIdentity, historic residential character]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNeighborhoodIdentity
Context triple: [Beaumont-Wilshire, hasNeighborhoodIdentity, historic residential character]
  • A. hasNeighbourhoodStatus
    Indicates that an entity has a particular status, classification, or condition specifically in relation to a given neighbourhood.
  • B. hasNeighbourhood
    Indicates that one entity is located within, or is associated with, a particular neighborhood area of another entity.
  • C. hasNeighborhoodAssociation
    Indicates that an entity is associated with, or falls under the jurisdiction of, a particular neighborhood association.
  • D. hasNeighborhoodAlong
    Indicates that one entity has a neighboring area or region that extends along the boundary or length of another entity.
  • E. hasIdentity
    Indicates that one entity is the same as, or is identified as, another specific entity or identifier.
  • 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_69c6880687b08190805278b504d1c92c completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6cd0fa5188190a23281cb09d98139 completed March 27, 2026, 6:31 p.m.
PD Predicate disambiguation batch_69c6ad0d3c1081908dadff7a6a054123 completed March 27, 2026, 4:15 p.m.
PDg Predicate description generation batch_69c6cd0d939081908ede0bb6ce19f559 completed March 27, 2026, 6:31 p.m.
Created at: March 27, 2026, 2:05 p.m.