Triple
T11549923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Selenga River |
E273863
|
entity |
| Predicate | dischargeContributionToLakeBaikal |
P100086
|
FINISHED |
| Object | largest single contributor of inflowing water |
—
|
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: largest single contributor of inflowing water | Statement: [Selenga River, dischargeContributionToLakeBaikal, largest single contributor of inflowing water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dischargeContributionToLakeBaikal Context triple: [Selenga River, dischargeContributionToLakeBaikal, largest single contributor of inflowing water]
-
A.
dischargeContribution
Indicates that one party fulfills or settles an owed contribution, obligation, or share toward another party or collective.
-
B.
recoveredFromLake
Indicates that something was retrieved or taken out from a lake.
-
C.
isHighAltitudeLake
Indicates that a lake is situated at a relatively high elevation above sea level.
-
D.
usesLakeFor
Indicates that an entity utilizes a lake as a resource or setting for some purpose, activity, or function.
-
E.
isAmongLargestHighAltitudeLakes
Indicates that a lake ranks among the largest lakes located at high altitudes.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886e615b08190a072924329a94a6a |
completed | April 10, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69d8087e57b48190a4c253dc0210f9d4 |
completed | April 9, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69d822f00a088190ac6b48e45e743899 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 8, 2026, 9:37 p.m.