Triple

T2851771
Position Surface form Disambiguated ID Type / Status
Subject SeaTac E63107 entity
Predicate locatedBetween P1262 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: [SeaTac, locatedBetween, Seattle]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Seattle
Context triple: [SeaTac, locatedBetween, 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 the largest city in Oregon, known for its vibrant arts scene, progressive culture, and lush green spaces in the Pacific Northwest.
  • D. Portland
    Portland is the largest city in the U.S. state of Maine, known for its historic waterfront, vibrant arts scene, and coastal New England charm.
  • E. 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.
  • 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_69ab4c407c408190857d25e027155ce9 completed March 6, 2026, 9:50 p.m.
NER Named-entity recognition batch_69abdf5ca2648190bd32c6ec4b0dd3b6 completed March 7, 2026, 8:18 a.m.
NED1 Entity disambiguation (via context triple) batch_69b20309280c8190ad9a73397e42267c completed March 12, 2026, 12:04 a.m.
Created at: March 6, 2026, 10:02 p.m.