Triple
T37943800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Navy of the Kingdom of Serbia |
E946552
|
entity |
| Predicate | notableRiverBase |
P162290
|
FINISHED |
| Object | Belgrade |
E24551
|
NE 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: Belgrade | Statement: [Navy of the Kingdom of Serbia, notableRiverBase, Belgrade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRiverBase Context triple: [Navy of the Kingdom of Serbia, notableRiverBase, Belgrade]
-
A.
raceRiver
Indicates that an entity participates in a race that takes place on or along a river.
-
B.
associatedRiverBasin
Indicates that one entity is linked to, or lies within the drainage area of, a particular river basin.
-
C.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
D.
useRiverSystems
chosen
Indicates that an entity utilizes or manages river systems for a particular purpose or function.
-
E.
feedsWatersThatReach
Indicates that one body of water supplies or contributes flow to other waters that it eventually reaches.
- F. None of above.
Provenance (4 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_69f76ef531ac8190ae6d99e5786e76ec |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a43e9d27fac81908fd32871b041d3a1 |
completed | June 30, 2026, 4:07 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.