Triple

T29624755
Position Surface form Disambiguated ID Type / Status
Subject Edo-dori E755105 entity
Predicate hasStreetTypeSuffix P67434 FINISHED
Object dori (Japanese for street/avenue) 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: dori (Japanese for street/avenue) | Statement: [Edo-dori, hasStreetTypeSuffix, dori (Japanese for street/avenue)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasStreetTypeSuffix
Context triple: [Edo-dori, hasStreetTypeSuffix, dori (Japanese for street/avenue)]
  • A. hasRoadSuffix chosen
    Indicates that a road or street name ends with a specific suffix (such as "Street", "Avenue", or "Boulevard").
  • B. streetAddressSuffix
    Indicates the trailing component of a street address, such as a directional or unit/lot/apartment designator that follows the main street address.
  • C. correspondsToStreetType
    Indicates that one entity matches or is associated with a particular type or classification of street.
  • D. hasStreetNamingPattern
    Indicates that there is a characteristic or systematic way in which streets are named in relation to a given entity.
  • E. hasSideStreetType
    Indicates that an entity (such as a street or road segment) is associated with a specific type or classification of side street.
  • 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_69f0ef86b6ec8190a87fff07fd983b1e completed April 28, 2026, 5:33 p.m.
NER Named-entity recognition batch_69fdd07a34c08190982b8c61c2775cf6 completed May 8, 2026, noon
PD Predicate disambiguation batch_69fdbd25c7908190b72fca8de7ce503f completed May 8, 2026, 10:38 a.m.
Created at: April 28, 2026, 6:37 p.m.