Triple
T31810780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pyasina Bay |
E811999
|
entity |
| Predicate | riverInput |
P178633
|
FINISHED |
| Object | freshwater inflow from Pyasina 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 inflow from Pyasina River | Statement: [Pyasina Bay, riverInput, freshwater inflow from Pyasina River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverInput Context triple: [Pyasina Bay, riverInput, freshwater inflow from Pyasina River]
-
A.
riverContext
Indicates a contextual or situational relationship involving a river, such as its surrounding environment, conditions, or relevant circumstances.
-
B.
riverControl
Indicates a relationship where one entity manages, regulates, or exerts authority over the flow, usage, or conditions of a river.
-
C.
riverManaged
Indicates that a river is subject to management, regulation, or oversight by a particular authority, organization, or system.
-
D.
raceRiver
Indicates that an entity participates in a race that takes place on or along a river.
-
E.
riverSystem
Indicates that one entity is a river system to which the other entity belongs or is a component (such as a tributary or segment).
- 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_69f348e846c081908eb468a0665afd55 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
| PDg | Predicate description generation | batch_69f7117cf2188190b29e36fc1e342c60 |
completed | May 3, 2026, 9:12 a.m. |
Created at: April 30, 2026, 11:43 p.m.