Triple
T37673050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volga–Kama river system |
E938013
|
entity |
| Predicate | majorConfluenceLocation |
P3421
|
FINISHED |
| Object | near Kazan |
—
|
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: near Kazan | Statement: [Volga–Kama river system, majorConfluenceLocation, near Kazan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorConfluenceLocation Context triple: [Volga–Kama river system, majorConfluenceLocation, near Kazan]
-
A.
confluenceLocation
chosen
Indicates the place where two or more flowing entities (such as rivers or streams) meet and merge.
-
B.
hasMajorLocation
Indicates that an entity is primarily situated in, based in, or most significantly associated with a particular location.
-
C.
locatedAtConfluenceOf
Indicates that something is situated at the meeting point where two or more bodies of water or similar flowing features join together.
-
D.
centralLocation
Indicates that one entity serves as the primary or central place associated with another entity.
-
E.
confluenceDistrict
Indicates a relationship where an area or region is designated as the district surrounding or encompassing the confluence of two or more water bodies.
- 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_69f76ed7b1408190ba8c93c53cb8becf |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00144238708190acbec3f791cc873e |
completed | May 10, 2026, 5:14 a.m. |
| PD | Predicate disambiguation | batch_6a00120244a4819090ef39070aba9d99 |
completed | May 10, 2026, 5:05 a.m. |
Created at: May 3, 2026, 4:18 p.m.