Triple

T2355491
Position Surface form Disambiguated ID Type / Status
Subject Charles Street, Boston E47542 entity
Predicate sidewalkMaterial P14456 FINISHED
Object brick (predominantly in Beacon Hill section) 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: brick (predominantly in Beacon Hill section) | Statement: [Charles Street, Boston, sidewalkMaterial, brick (predominantly in Beacon Hill section)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: sidewalkMaterial
Context triple: [Charles Street, Boston, sidewalkMaterial, brick (predominantly in Beacon Hill section)]
  • A. hasSidewalk
    Indicates that a location, path, or roadway is accompanied by a designated sidewalk area for pedestrian use.
  • B. pavedWith chosen
    Indicates that a surface or area is covered or constructed using a specified material as its paving.
  • C. exteriorMaterial
    Indicates the material that forms the outer surface or outer construction of an object or structure.
  • D. hasFloorMaterial
    Indicates that an entity’s floor is made of, covered with, or constructed from a specified material.
  • E. frontageMaterial
    Indicates the material used on the exterior front-facing surface of a structure or property.
  • 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_69a88a1b678c8190bce986922ba60ce0 completed March 4, 2026, 7:38 p.m.
NER Named-entity recognition batch_69abcb802da08190980100444010f91e completed March 7, 2026, 6:53 a.m.
PD Predicate disambiguation batch_69abc5981ce48190a3f7852d28276e11 completed March 7, 2026, 6:28 a.m.
Created at: March 4, 2026, 7:54 p.m.