Triple

T6144020
Position Surface form Disambiguated ID Type / Status
Subject Puget Sound lowland forests E137029 entity
Predicate majorCityWithin P9892 FINISHED
Object Tacoma E21347 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: Tacoma | Statement: [Puget Sound lowland forests, majorCityWithin, Tacoma]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tacoma
Context triple: [Puget Sound lowland forests, majorCityWithin, Tacoma]
  • A. Tacoma
    Tacoma is a small suburb on the Central Coast of New South Wales, Australia, situated along the Wyong River near Tuggerah Lake.
  • B. Tacoma, Washington chosen
    Tacoma, Washington is a mid-sized port city in the Pacific Northwest known for its waterfront, industrial history, and vibrant arts and museum scene.
  • C. Bellingham
    Bellingham is a residential district in southeast London known for its 20th-century housing estates and local community amenities.
  • D. Tukwila
    Tukwila is a suburban city just south of Seattle, Washington, known as a regional transportation and retail hub.
  • E. SeaTac
    SeaTac is a city in Washington State located between Seattle and Tacoma, best known for housing Seattle–Tacoma International Airport and being served by regional light rail.
  • 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_69c008a2c6308190a56519b22d55d083 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c060fca4cc8190bf95231cd2a594c1 completed March 22, 2026, 9:37 p.m.
NED1 Entity disambiguation (via context triple) batch_69c72f6514948190a5562201e7b36e27 completed March 28, 2026, 1:31 a.m.
Created at: March 22, 2026, 4:16 p.m.