Triple
T16837079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manas Lake |
E409310
|
entity |
| Predicate | hasNoSurfaceOutflow |
P125048
|
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: [Manas Lake, hasNoSurfaceOutflow, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoSurfaceOutflow Context triple: [Manas Lake, hasNoSurfaceOutflow, true]
-
A.
hasFlowRegime
Indicates that one entity is characterized by, or operates under, a particular pattern or regime of flow.
-
B.
hasMajorOutflowBasin
Indicates that a geographic feature (such as a water body or watershed) has a specific basin into which most or all of its water ultimately flows.
-
C.
hasInlet
Indicates that one entity serves as an inlet or entry point through which another entity receives a flow of material, energy, or fluid.
-
D.
hasSurfaceConnections
Indicates that one entity is linked to another through connections or interfaces that occur at or across their surfaces.
-
E.
hasSurfaceLevel
Indicates that one entity possesses or is characterized by a particular degree or measure of surface level (e.g., depth, detail, or superficiality).
- F. None of above. chosen
Provenance (4 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_69d883952b048190887740a980b712ed |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b34e080c8190bf7a236205b41db2 |
completed | April 18, 2026, 4:37 p.m. |
| PD | Predicate disambiguation | batch_69e32b87b4248190aaddb05e88452356 |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e34fb7c8c8819086975b7955b7d8ef |
completed | April 18, 2026, 9:32 a.m. |
Created at: April 10, 2026, 5:23 a.m.