Triple
T20377930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Keowee |
E497741
|
entity |
| Predicate | waterQualityCharacteristic |
P60967
|
FINISHED |
| Object | clear 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: clear water | Statement: [Lake Keowee, waterQualityCharacteristic, clear water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterQualityCharacteristic Context triple: [Lake Keowee, waterQualityCharacteristic, clear water]
-
A.
hasWaterCharacteristics
Indicates that one entity possesses qualities, properties, or behaviors characteristic of water.
-
B.
waterAppearance
chosen
Indicates how the water involved in the situation looks or visually appears (e.g., its color, clarity, or surface condition).
-
C.
waterCondition
Indicates the state or quality of water affecting an entity, such as its cleanliness, safety, or suitability for a particular use.
-
D.
hasWaterQualityDesignation
Indicates that an entity has been assigned a specific official classification or status regarding its water quality.
-
E.
waterQualityIssues
Indicates that there are problems or concerns with the condition, safety, or suitability of a water source.
- 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_69e0b4a5b7908190a972e4e7e698ae94 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e678ae3468819087d7db7e1b79efc7 |
completed | April 20, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69e57648be3c81908256838228cabf5c |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:27 a.m.