Triple
T38512635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Selenge River basin |
E921953
|
entity |
| Predicate | isMainSurfaceInflowOf |
P4496
|
FINISHED |
| Object | Lake Baikal |
—
|
NE NERFINISHED |
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: Lake Baikal | Statement: [Selenge River basin, isMainSurfaceInflowOf, Lake Baikal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMainSurfaceInflowOf Context triple: [Selenge River basin, isMainSurfaceInflowOf, Lake Baikal]
-
A.
hasPrimaryInflow
chosen
Indicates that one entity serves as the main source of inflowing material, energy, or influence into another entity.
-
B.
mainInflowFrom
Indicates that the primary source or largest contributing inflow to something (e.g., a body, system, or process) comes from a specified origin.
-
C.
inflowTo
Indicates that something (such as a fluid, resource, or quantity) flows or moves into a specified target or destination.
-
D.
secondaryInflow
Indicates an additional, non-primary flow of something (such as water, resources, or information) entering a main system or channel.
-
E.
hasNoSurfaceOutflow
Indicates that the entity does not discharge water or other contents to an external surface outlet, such as a river, stream, or ocean.
- 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_69f76ea3c5448190aa7002fc1ba3f874 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:32 p.m.