Triple
T23803872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wahkiakum tribe |
E589646
|
entity |
| Predicate | regionNowWithin |
P46950
|
FINISHED |
| Object | Wahkiakum County, Washington |
—
|
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: Wahkiakum County, Washington | Statement: [Wahkiakum tribe, regionNowWithin, Wahkiakum County, Washington]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionNowWithin Context triple: [Wahkiakum tribe, regionNowWithin, Wahkiakum County, Washington]
-
A.
regionFrom
Indicates that something originates from, is derived from, or is associated with a particular geographic or administrative region.
-
B.
realmWithin
chosen
Indicates that one realm or domain is contained inside, or exists as a subset of, another realm or domain.
-
C.
endsInRegion
Indicates that an entity’s spatial or temporal extent terminates within the boundaries of a specified region.
-
D.
isRegionOf
Indicates that one entity is a geographic or administrative region belonging to, contained within, or associated with another entity.
-
E.
regionException
Indicates an exception or exclusion to a rule, condition, or classification that applies specifically to a certain region or set of regions.
- 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_69e25d19fecc8190a5cf39bbb18d5d7f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c750048c8190899ff611df35b361 |
completed | April 29, 2026, 8:54 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:55 p.m.