Triple
T15553978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alapaha River |
E370819
|
entity |
| Predicate | hasWaterQualityCharacteristic |
P108980
|
FINISHED |
| Object | acidic |
—
|
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: acidic | Statement: [Alapaha River, hasWaterQualityCharacteristic, acidic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWaterQualityCharacteristic Context triple: [Alapaha River, hasWaterQualityCharacteristic, acidic]
-
A.
hasWaterCharacteristics
Indicates that one entity possesses qualities, properties, or behaviors characteristic of water.
-
B.
hasWaterQualityDesignation
chosen
Indicates that an entity has been assigned a specific official classification or status regarding its water quality.
-
C.
hasWaterQualityHistory
Indicates that an entity is associated with a record or series of records describing changes or measurements of its water quality over time.
-
D.
hasWaterBodyCharacteristic
Indicates that a water body possesses a specified physical, chemical, or ecological characteristic.
-
E.
hasWatershedCharacteristic
Indicates that a watershed possesses a specified characteristic, feature, or property.
- 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_69d85cc6cf40819091f4a5facee1ebe6 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04a96c0c88190808f68601a36b506 |
completed | April 16, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69deda7e6e748190b29ccce23298afef |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:09 a.m.