Triple

T34994506
Position Surface form Disambiguated ID Type / Status
Subject Calgary–Lethbridge E1009485 entity
Predicate majorUrbanCentreLinked P92119 FINISHED
Object Calgary NE NERFINISHED

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: Calgary | Statement: [Calgary–Lethbridge, majorUrbanCentreLinked, Calgary]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: majorUrbanCentreLinked
Context triple: [Calgary–Lethbridge, majorUrbanCentreLinked, Calgary]
  • A. linkedCity
    Indicates that two entities are associated with each other through a specific city, such as being located in, connected via, or related by that city.
  • B. majorUrbanCenterIn
    Indicates that a city or metropolitan area functions as a primary or significant urban center within the specified region or administrative unit.
  • C. relatedUrbanArea chosen
    Indicates that one urban area is geographically or functionally associated with another urban area, such as being nearby, connected, or part of the same broader metropolitan context.
  • D. linksMetropolitanArea
    Indicates a relationship where one entity connects or associates a subject with a specific metropolitan area.
  • E. linkedToCapitalCity
    Indicates a relationship where an entity is associated or connected to a capital city, typically as its relevant or corresponding urban center.
  • 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_69f76dca50dc8190b71f39defe186be8 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69ff76ac40988190a34d858b5472ee2b completed May 9, 2026, 6:02 p.m.
PD Predicate disambiguation batch_69ff760a90948190a12fcb80e6e3e14b completed May 9, 2026, 5:59 p.m.
Created at: May 3, 2026, 4:01 p.m.