Triple
T9887331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tumwater Falls |
E180966
|
entity |
| Predicate | salmonRun |
P91615
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Tumwater Falls, salmonRun, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: salmonRun Context triple: [Tumwater Falls, salmonRun, yes]
-
A.
salmonType
Indicates that one entity is classified as a specific type or variety of salmon in relation to another entity.
-
B.
runOfTheRiver
Indicates a relationship where a hydroelectric facility operates using the natural flow and elevation drop of a river without significant water storage or regulation by a large reservoir.
-
C.
hasSteelheadRun
Indicates that a location or waterway supports or experiences a migratory run of steelhead trout.
-
D.
runs
Indicates that an entity moves swiftly on foot, typically using its legs in a continuous, rapid motion.
-
E.
hauls
Indicates that one entity pulls, drags, or transports another entity, typically involving effort or force over a distance.
- F. None of above. chosen
Provenance (4 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_69ca828082cc8190a40f8d299caa6545 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb457c8cc81909d211d5882228076 |
completed | April 2, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69cd1d810ed48190a252b70e9390c8f3 |
completed | April 1, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69cd36f112bc81908b473787e702de2f |
completed | April 1, 2026, 3:17 p.m. |
Created at: March 30, 2026, 8:39 p.m.