Triple
T20323535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washoe Lake |
E492269
|
entity |
| Predicate | canExperience |
P138332
|
FINISHED |
| Object | significant water level fluctuations |
—
|
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: significant water level fluctuations | Statement: [Washoe Lake, canExperience, significant water level fluctuations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canExperience Context triple: [Washoe Lake, canExperience, significant water level fluctuations]
-
A.
mayExperience
chosen
Indicates that an entity is capable of undergoing, feeling, or being subject to a particular event, state, or condition.
-
B.
providesExperienceOf
Indicates that one entity enables or delivers the experience of another entity to someone or something.
-
C.
experienceFeature
Indicates that an entity undergoes, encounters, or makes use of a particular feature.
-
D.
experiences
Indicates that an entity undergoes, feels, or is affected by a particular event, state, or condition.
-
E.
hasAlternateExperience
Indicates that an entity is associated with a different or substitute experience relative to a primary or standard one.
- 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6778d95dc81909b1c87d26b5d3a33 |
completed | April 20, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e5762655ac8190a8cc48a29fa2c0c4 |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:21 a.m.