Triple

T30419790
Position Surface form Disambiguated ID Type / Status
Subject Bank Street, Clayton E773865 entity
Predicate hasAddressRole P184606 FINISHED
Object forms part of local addressing system in Clayton 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: forms part of local addressing system in Clayton | Statement: [Bank Street, Clayton, hasAddressRole, forms part of local addressing system in Clayton]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAddressRole
Context triple: [Bank Street, Clayton, hasAddressRole, forms part of local addressing system in Clayton]
  • A. hasAddress
    Indicates that an entity is associated with a specific address or location.
  • B. addressRole
    Indicates the specific function or capacity an entity has in relation to a given address (e.g., owner, recipient, billing contact).
  • C. hasAddressState
    Indicates that an entity’s address is located within a particular state or state-level administrative region.
  • D. addressesRole
    Indicates that one entity directs communication, content, or action specifically toward another entity in its capacity or function as a particular role.
  • E. addressedWith
    Indicates that one entity is referred to or spoken to using a particular name, title, or form of address.
  • 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_69f22491ba248190b9a4776ca8e42d02 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f7b365288c8190bcb11fcfba028737 completed May 3, 2026, 8:43 p.m.
PD Predicate disambiguation batch_69f7b1b8a9fc8190a1279e67a2d12707 completed May 3, 2026, 8:36 p.m.
PDg Predicate description generation batch_69f7b2f2b9ac8190aa05b8a1aa18ec2d completed May 3, 2026, 8:41 p.m.
Created at: April 29, 2026, 8:05 p.m.