Triple
T29802650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quileute Indian Reservation |
E756747
|
entity |
| Predicate | borderWithBodyOfWater |
P122362
|
FINISHED |
| Object | Quillayute River |
—
|
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: Quillayute River | Statement: [Quileute Indian Reservation, borderWithBodyOfWater, Quillayute River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderWithBodyOfWater Context triple: [Quileute Indian Reservation, borderWithBodyOfWater, Quillayute River]
-
A.
hasBodyOfWaterType
Indicates that a body of water is classified as being of a particular type or category (such as lake, river, ocean, etc.).
-
B.
adjacentToBodyOfWater
Indicates that one entity is directly next to or bordering a body of water, such as a lake, river, or ocean.
-
C.
borderingWaters
chosen
Indicates that a geographic area directly touches or is adjacent to a particular body of water.
-
D.
borderedBySeaViaRiverMouth
Indicates that a place is bordered by the sea specifically at the point where a river flows into it (its river mouth).
-
E.
involvesBodyOfWater
Indicates that the relationship or event includes, affects, or takes place in connection with a body of water such as a sea, lake, river, or ocean.
- 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_69f2245584848190ad4cab1f07752ccb |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fe031bc6208190860099aef72d8dcb |
completed | May 8, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69fe014c8b388190b5d4e0cb95ee2be5 |
completed | May 8, 2026, 3:29 p.m. |
Created at: April 29, 2026, 5:19 p.m.