Triple
T30268639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoh Tribe |
E769723
|
entity |
| Predicate | reservationLocatedOn |
P34578
|
FINISHED |
| Object | Hoh River mouth |
—
|
LITERAL 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: Hoh River mouth | Statement: [Hoh Tribe, reservationLocatedOn, Hoh River mouth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reservationLocatedOn Context triple: [Hoh Tribe, reservationLocatedOn, Hoh River mouth]
-
A.
reservationLocatedIn
Indicates that a reservation (such as a booking or held resource) is situated within or associated with a specific location or place.
-
B.
reservationLocatedAlong
chosen
Indicates that a reservation is situated along, adjacent to, or following the course or extent of a specified linear feature such as a road, river, or boundary.
-
C.
reservationNear
Indicates that a reservation is located geographically close to a specified reference entity or place.
-
D.
reservationEstablishedIn
Indicates that a reservation (such as a booking or protected area) was created, set up, or formally established in a particular place or context.
-
E.
reservationAlsoKnownAs
Indicates that a reservation is referred to by an alternative name or alias.
- 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_69f224856d9881908c7f0dd64f059672 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f680d27d288190b66d52f002726551 |
completed | May 2, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:43 p.m.