Triple
T16708286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aro River |
E406028
|
entity |
| Predicate | hasFreshwaterType |
P25292
|
FINISHED |
| Object | freshwater river |
—
|
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: freshwater river | Statement: [Aro River, hasFreshwaterType, freshwater river]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFreshwaterType Context triple: [Aro River, hasFreshwaterType, freshwater river]
-
A.
hasFreshwaterSection
Indicates that an entity includes or contains a distinct section or area composed of freshwater.
-
B.
isFreshwaterBody
chosen
Indicates that the referenced body of water consists primarily of non-saline (fresh) water rather than saltwater.
-
C.
receivesFreshwaterFrom
Indicates that one entity is supplied with or obtains freshwater from another entity as its source.
-
D.
hasAquaticEcosystem
Indicates that an entity possesses, contains, or is associated with an ecosystem primarily based in water (such as rivers, lakes, wetlands, or oceans).
-
E.
hasFreshwaterLake
Indicates that one entity possesses, contains, or is associated with a freshwater lake.
- 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_69d8838db21081909589220fd71440a4 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e38337ecac8190bc4a9410ed7681ab |
completed | April 18, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69e319c379f88190ac0adf812486f598 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:20 a.m.