Triple
T12708017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Medicine Creek |
E303639
|
entity |
| Predicate | party |
P1790
|
FINISHED |
| Object | Puyallup |
E284955
|
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: Puyallup | Statement: [Treaty of Medicine Creek, party, Puyallup]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Puyallup Context triple: [Treaty of Medicine Creek, party, Puyallup]
-
A.
Puyallup
chosen
Puyallup is a city in Washington State known for its annual Washington State Fair and its location in the Puyallup River Valley southeast of Tacoma.
-
B.
Poulsbo
Poulsbo is a small waterfront city in Washington State known for its Scandinavian heritage and charming downtown on Liberty Bay.
-
C.
Ellensburg
Ellensburg is a small city in central Washington known for hosting Central Washington University and its historic downtown and rodeo traditions.
-
D.
Tukwila
Tukwila is a suburban city just south of Seattle, Washington, known as a regional transportation and retail hub.
-
E.
Bellingham
Bellingham is a residential district in southeast London known for its 20th-century housing estates and local community amenities.
- 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_69d7bdef90d48190b46b88270e780946 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9620663e881908d367170ed6d2c81 |
completed | April 10, 2026, 8:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff3643a23481909103166abb6aaa4e |
completed | May 9, 2026, 1:27 p.m. |
Created at: April 9, 2026, 5:23 p.m.