Triple
T71217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soda Lake (San Bernardino County) |
E1424
|
entity |
| Predicate | formationProcess |
P972
|
FINISHED |
| Object | evaporation of standing water |
—
|
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: evaporation of standing water | Statement: [Soda Lake (San Bernardino County), formationProcess, evaporation of standing water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formationProcess Context triple: [Soda Lake (San Bernardino County), formationProcess, evaporation of standing water]
-
A.
formationEvent
Indicates the event or process through which something comes into existence, is created, or is initially established.
-
B.
constructionMethod
Indicates the technique or process by which something is built, assembled, or created.
-
C.
formedBy
chosen
Indicates that something comes into existence or is created as a result of a specific agent, process, or combination of components.
-
D.
growthForm
Indicates the physical structure or habit in which something develops or grows (such as its overall shape, form, or growth pattern).
-
E.
shape
Indicates that one entity has a particular geometric or physical form characterized by the other entity.
- 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_69a24c06b3bc8190aa4ac89026115efc |
completed | Feb. 28, 2026, 1:59 a.m. |
| NER | Named-entity recognition | batch_69a24f6997c081908b202f937eb2b14f |
completed | Feb. 28, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69a24eab7f408190a8275cb82474f575 |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:03 a.m.