Triple

T1683312
Position Surface form Disambiguated ID Type / Status
Subject Eastern Toronto E36384 entity
Predicate isCommonlyDefinedBy P32719 FINISHED
Object areas east of the Don River within Toronto 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: areas east of the Don River within Toronto | Statement: [Eastern Toronto, isCommonlyDefinedBy, areas east of the Don River within Toronto]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isCommonlyDefinedBy
Context triple: [Eastern Toronto, isCommonlyDefinedBy, areas east of the Don River within Toronto]
  • A. commonIn
    Indicates that something frequently occurs, appears, or is found within a specified context, group, or environment.
  • B. areDefinedIn
    Indicates that the referenced entities are specified, described, or formally established within a particular source, context, or scope.
  • C. isSharedBy
    Indicates that something is jointly possessed, used, or experienced by two or more entities.
  • D. isLessCommonThan
    Indicates that one item occurs, appears, or is observed less frequently than another item.
  • E. equivalentTo
    Indicates that two entities represent the same concept, value, or state, and can be treated as interchangeable in the given context.
  • 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_69a886139ed081909af0940aa9313512 completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69aba644070c81908745b56d981fe273 completed March 7, 2026, 4:15 a.m.
PD Predicate disambiguation batch_69aa61b57a6881909373af287ef24799 completed March 6, 2026, 5:10 a.m.
PDg Predicate description generation batch_69aba641e6a881909645577e72b53df2 completed March 7, 2026, 4:14 a.m.
Created at: March 4, 2026, 7:29 p.m.