Triple
T13044880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Putrid Sea |
E327290
|
entity |
| Predicate | isEndorheicOrPoorlyFlushed |
P29761
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Putrid Sea, isEndorheicOrPoorlyFlushed, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEndorheicOrPoorlyFlushed Context triple: [Putrid Sea, isEndorheicOrPoorlyFlushed, true]
-
A.
hydrologicallyIsolatedFrom
chosen
Indicates that one water body or hydrological feature has no direct surface or subsurface water connection or exchange with another.
-
B.
hasBodyOfWaterDrainedBy
Indicates that a body of water is emptied or its water flow is carried away by a specified draining feature, such as a river, channel, or drainage system.
-
C.
receivesFreshwaterFrom
Indicates that one entity is supplied with or obtains freshwater from another entity as its source.
-
D.
isFreshwaterBody
Indicates that the referenced body of water consists primarily of non-saline (fresh) water rather than saltwater.
-
E.
hasWetlandsAtMouth
Indicates that a watercourse or water body has wetlands located at or surrounding its mouth where it meets another body of water.
- 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_69d8076e64308190904fb5c93517c901 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d98a9829b48190b23624b6b3df4600 |
completed | April 10, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69d9803aca4c8190b1015cd159cc47a9 |
completed | April 10, 2026, 10:56 p.m. |
Created at: April 9, 2026, 8:56 p.m.