Triple
T29793378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sremska Mitrovica na Savi |
E756472
|
entity |
| Predicate | indicatesLocationRelativeTo |
P7317
|
FINISHED |
| Object | Sava River |
—
|
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: Sava River | Statement: [Sremska Mitrovica na Savi, indicatesLocationRelativeTo, Sava River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indicatesLocationRelativeTo Context triple: [Sremska Mitrovica na Savi, indicatesLocationRelativeTo, Sava River]
-
A.
hasRelativeLocation
chosen
Indicates that one entity is positioned in space in relation to another entity’s location.
-
B.
positionedRelativeTo
Indicates that one entity’s spatial location is defined or described in relation to the position of another entity.
-
C.
isRelativeTo
Indicates that one entity has a familial or kinship relationship to another entity.
-
D.
refersToLocation
Indicates that one entity designates, points to, or identifies a specific location associated with it.
-
E.
locationRelativeToBorder
Indicates the position or placement of something in relation to a specified border or boundary.
- 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_69f22454583081908927516cb9938d1d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f674e4bb8c8190baf5c9fbfe45e4e1 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 5:13 p.m.