Triple
T33817443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gorst, Washington |
E866727
|
entity |
| Predicate | locatedOnInletOf |
P206680
|
FINISHED |
| Object | Puget Sound |
E40985
|
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: Puget Sound | Statement: [Gorst, Washington, locatedOnInletOf, Puget Sound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnInletOf Context triple: [Gorst, Washington, locatedOnInletOf, Puget Sound]
-
A.
locatedAtOutletOf
Indicates that one entity is positioned at or directly adjacent to the outlet or discharge point of another entity (such as a flow, channel, or system).
-
B.
inletType
Indicates the specific kind or category of inlet through which something (such as a fluid, signal, or material) enters a system or component.
-
C.
locatedInTheInteriorOf
Indicates that one entity is situated entirely within the inner part or inside area of another entity, rather than on its surface or boundary.
-
D.
intakeLocation
Indicates the place or facility where an entity is initially received, admitted, or taken in.
-
E.
locatedAtConfluenceOf
Indicates that something is situated at the meeting point where two or more bodies of water or similar flowing features join together.
- F. None of above. chosen
Provenance (5 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_69f349911a8c81908478662194b23d8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a366e9cb9008190ab758e77985575e5 |
completed | June 20, 2026, 10:42 a.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037e07fe4481909ca21eae7a941ee7 |
completed | May 12, 2026, 7:22 p.m. |
Created at: May 1, 2026, 1:46 a.m.