Triple
T8871992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ribnica Bridge |
E211178
|
entity |
| Predicate | hasNearbyConfluence |
P39585
|
FINISHED |
| Object | confluence of Ribnica River and Morača 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: confluence of Ribnica River and Morača River | Statement: [Ribnica Bridge, hasNearbyConfluence, confluence of Ribnica River and Morača River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyConfluence Context triple: [Ribnica Bridge, hasNearbyConfluence, confluence of Ribnica River and Morača River]
-
A.
nearbyTo
Indicates that one entity is located close in distance or position to another entity.
-
B.
hasNearbyTrail
Indicates that one entity is located close to or within a short distance of a trail.
-
C.
hasNearbyTrailheadFor
Indicates that one location has a trailhead situated close enough to serve as a convenient access point for another location.
-
D.
hasNotableNearbyEntity
chosen
Indicates that one entity has another significant or noteworthy entity located in its close physical or contextual proximity.
-
E.
hasNearbyCommon
Indicates that two entities share at least one common element, feature, or connection that is located within a specified nearby distance or vicinity.
- 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_69ca838e78748190934d82db3104f855 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc61281e888190a32b08980310979f |
completed | April 1, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2956788190a311c647b4da17a6 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:51 p.m.