Triple

T787218
Position Surface form Disambiguated ID Type / Status
Subject William H. Foege Global Health Building E16830 entity
Predicate locatedIn P40 FINISHED
Object Seattle E166067 NE 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: Seattle | Statement: [William H. Foege Global Health Building, locatedIn, Seattle]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Seattle
Context triple: [William H. Foege Global Health Building, locatedIn, Seattle]
  • A. Seattle chosen
    Seattle is a major coastal city in the U.S. state of Washington, known for its tech industry, vibrant music and arts scene, and iconic landmarks like the Space Needle.
  • B. Tukwila
    Tukwila is a suburban city just south of Seattle, Washington, known as a regional transportation and retail hub.
  • C. Portland
    Portland is a small historic town in the Central Tablelands region of New South Wales, Australia, known for its early cement works and heritage streetscapes.
  • D. Bellevue
    Bellevue is a small municipality located along Lake Geneva in the canton of Geneva in southwestern Switzerland.
  • E. Renton
    Renton is a suburban city in Washington State located just southeast of Seattle, known for its Boeing facilities and position at the south end of Lake Washington.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69a4936cb7448190914f5fe4b8d81607 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4a78171908190a38a70274bfbebf9 completed March 1, 2026, 8:54 p.m.
NED1 Entity disambiguation (via context triple) batch_69ad3072c3a881908c33159cdd55ae0b completed March 8, 2026, 8:16 a.m.
Created at: March 1, 2026, 7:38 p.m.