Triple
T20328096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nitra River |
E492393
|
entity |
| Predicate | confluenceWithVáhLocation |
P2416
|
FINISHED |
| Object | near Komoča |
—
|
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 Komoča | Statement: [Nitra River, confluenceWithVáhLocation, near Komoča]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confluenceWithVáhLocation Context triple: [Nitra River, confluenceWithVáhLocation, near Komoča]
-
A.
confluenceWith
chosen
Indicates that one entity joins or merges together with another, typically at a shared meeting point.
-
B.
locatedAtConfluenceOf
Indicates that something is situated at the meeting point where two or more bodies of water or similar flowing features join together.
-
C.
confluenceLocation
Indicates the place where two or more flowing entities (such as rivers or streams) meet and merge.
-
D.
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.
-
E.
isBelievedToBeConfluenceOf
Indicates that something is regarded or considered to be the point where multiple elements, sources, or influences come together.
- 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e677e513608190b70527cd9f4d5da3 |
completed | April 20, 2026, 7 p.m. |
| PD | Predicate disambiguation | batch_69e5762655ac8190a8cc48a29fa2c0c4 |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:21 a.m.